On Wed, Nov 26, 2008 at 11:56 PM, Udo Richter <udo_richter@xxxxxx> wrote:
Without knowing enough about the differences between -S and -S2 tuners
and whatever cards are on the market, I'll try to step back and give
this my 2c point of view:
What does a DVB app need to know? A DVB app probably just needs to know
"What devices are capable of tuning to channel XYZ?". The API could
answer this the same way as it would tune to channel XYZ, just without
actually doing it. Try-before-you-buy.
This would also give maximum flexibility to the driver, as a device that
supports some -S2 features could offer these, or a device that has known
bugs on some tuning modes could also deny these. Non-standard modes
could be offered without requiring yet another FE_CAN_XYZ.
Assuming you have 3 cards, one DVB-S2 and 2xDVB-S.
In case of DVB-S channel, all the cards will be able to record it, what will be the decision? Random?
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.
I agree that driver should tell whenever it able to tune to a channel when its ordered to perform tuning. There shouldn't be any guess just by checking the LOCK status.
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
