<div dir="ltr"><br>
<div class="gmail_quote">On Wed, Nov 26, 2008 at 11:56 PM, Udo Richter <span dir="ltr">&lt;<a href="mailto:udo_richter@gmx.de">udo_richter@gmx.de</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Without knowing enough about the differences between -S and -S2 tuners<br>and whatever cards are on the market, I&#39;ll try to step back and give<br>
this my 2c point of view:<br><br>What does a DVB app need to know? A DVB app probably just needs to know<br>&quot;What devices are capable of tuning to channel XYZ?&quot;. The API could<br>answer this the same way as it would tune to channel XYZ, just without<br>
actually doing it. Try-before-you-buy.<br><br>This would also give maximum flexibility to the driver, as a device that<br>supports some -S2 features could offer these, or a device that has known<br>bugs on some tuning modes could also deny these. Non-standard modes<br>
could be offered without requiring yet another FE_CAN_XYZ.</blockquote>
<div>Assuming you have 3 cards, one DVB-S2 and 2xDVB-S.</div>
<div>In case of DVB-S channel, all the cards will be able to record it, what will be the decision? Random?</div>
<div>You might select DVB-S2 card for DVB-S recording, while it might be used to record DVB-S2 channel that no other card is capable to do.</div>
<div>&nbsp;</div>
<div>I agree that driver should tell whenever it able to tune to a channel when its ordered to perform tuning. There shouldn&#39;t be any guess just by checking the LOCK status.</div>
<div>&nbsp;</div></div></div>