Re: [PATCH 0/5] Driver support for cards based on Digital Devices bridge (ddbridge)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Oliver Endriss writes:
 > > Both ngene and ddbrige calls dvb_attach once for drxk_attach.
 > > The logic used there, and by tda18271c2dd driver is different
 > > from similar logic on other frontends.
 > > 
 > > The right fix is to change them to use the same logic, but,
 > > while we don't do that, we need to patch em28xx-dvb in order
 > > to do cope with ngene/ddbridge magic.
 > 
 > I disagree: The right fix is to extend the framework, and drop the
 > secondary frondend completely. The current way of supporting
 > multi-standard tuners is abusing the DVB API.
 > 

Yes, exactly what I wanted to say.

I am just working on yet another C/T combo. This time stv0367 and
TDA18212. For both there are existing drivers and our own version again.
I am trying to merge them so that there is not yet another
discussion regarding new driver versions (but the very first version
might still come out with separate drivers).
At the same time I want to add delivery system properties to 
support everything in one frontend device.
Adding a parameter to select C or T as default should help in most
cases where the application does not support switching yet.

Regards,
Ralph

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux