On Sun, Sep 14, 2008 at 1:31 AM, Manu Abraham <abraham.manu@xxxxxxxxx> wrote: > Markus Rechberger wrote: >> On Sun, Sep 14, 2008 at 12:46 AM, Manu Abraham <abraham.manu@xxxxxxxxx> wrote: >>> Markus Rechberger wrote: >>> >>>> How many devices are currently supported by the multiproto API >>>> compared with the s2 tree? >>> The initial set of DVB-S2 multistandard devices supported by the >>> multiproto tree is follows. This is just the stb0899 based dvb-s2 driver >>> alone. There are more additions by 2 more modules (not devices), but for >>> the simple comparison here is the quick list of them, for which some of >>> the manufacturers have shown support in some way. (There has been quite >>> some contributions from the community as well.): >>> >>> (Also to be noted is that, some BSD chaps also have shown interest in >>> the same) >>> >> >> they're heavy into moving the whole framework over as far as I've seen >> yes, also including yet unmerged drivers. > > > Using the same interface, the same applications will work there as well > which is a bonus, but isn't the existing user interface GPL ? (A bit > confused on that aspect) > I think it's good to have something that competes with Linux, I talked to some guys at that front too, and they seem to work close with application developers too As for the em28xx driver I agreed with pushing all my code (in case of linux, which includes unmerged independent drivercode from manufacturers) into their system using their license. > >>> * STB0899 based >>> >>> Anubis >>> Typhoon DVB-S2 PCI >>> >>> Azurewave/Twinhan >>> VP-1041 >>> VP-7050 >>> >>> Digital Now >>> AD SP400 >>> AD SB300 >>> >>> KNC1 >>> TV Station DVB-S2 >>> TV Station DVB-S2 Plus >>> >>> Pinnacle >>> PCTV Sat HDTV Pro USB 452e >>> >>> Satelco >>> TV Station DVB-S2 >>> Easywatch HDTV USB CI >>> Easywatch HDTV PCI >>> >>> Technisat >>> Skystar HD >>> Skystar HD2 >>> Skystar USB2 HDCI >>> >>> Technotrend >>> TT S2 3200 >>> TT S2 3600 >>> TT S2 3650 >>> >>> Terratec >>> Cinergy S2 PCI HD >>> Cinergy S2 PCI HDCI >>> >> >> those are pullable now against the current tree? > > > These devices, depend upon the DVB API update without which it wouldn't > work as they depend heavily on the DVB API framework. Without the > updated framework, it doesn't make any sense to pull them: they won't > even compile. The last but not least reason is that, the stb0899 driver > is a DVB-S2 multistandard device which requires DVB-S2/DSS support > additionally. > as far as I understood here it's that alot code is already available and has been tested for a couple of years, a few guys are trying to run their own game since they already have "some" code, and the problem is that people would have to port your drivers to the other system without your support. We've seen the same issue with the em28xx a year ago, although this one is participating at the BSD and OSX project now too (which takes the same source and makes alot more sence in terms of contributions). As soon as the em28xx code supports the mt2060 and saa7114 devices it would be ready to go into the kernel again separated from linuxtv... Markus _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
