[linux-dvb] [PATCH] Multi protocol support (stage #1)

Alan Nisota alannisota at gmail.com
Mon Jun 12 02:54:35 CEST 2006

Well, as it didn't seem that S2 was going anywhere, I had lost track
of this conversation a month or so ago, but now that I had to do some
mythtv work, I am trying to catch up.  I've looked over Manu's patch,
and associated sample app, and I don't think I really understand how
this method is supposed to work.
Specifically, if I have an app that needs to support the current API,
and want to add support for new card features, how do I use the new
As far as I can tell, I would replace FE_SET_FRONTEND with
FE_SET_PARAMS when actually doing a tune?
Is the expectation that we would use this for all cards (in which case
we need to support the old FE_SET_FRONTEND and FE_SET_PARAMS for all
current DVB-S/T/C and ATSC cards)? or just for new features not
supported by cards already using FE_SET_FRONTEND?  Also, will
FE_SET_PARAMS backfill the dvb_frontend_parameters field, or do all
current frontends need to be updated to support the new method?  And
in a related question, how do I determine which API I should be using
for a given card?  We had previously introduced the
'FE_HAS_EXTENDED_INFO' capability for this, but I don't see anything
equivalent in the latest revision.

Sorry if this is supposed to be obvious,  I'm just having trouble
seeing the big picture here.

Those of us using the genpix cards (subset of DVB-S2) have had to live
in our own little world in order to watch HD for 3 months now, and I'd
love to see a path leading to get the S2 capabilities into the kernel
sooner rather than later.

If there is any way I can be useful to getting a consensus and moving
forward, please let me know.  I'll be happy to fill in the necessary
code to make the current implementation usable by apps (specifically
VDR and MythTV), but there isn't much point if there isn't a growing
consensus that the current path is the right one.


More information about the linux-dvb mailing list