Hi, Manu is it possible to patch scan2 for dvb-s2 support ? Goga > Greetings. > > First I would like to thank everyone for their patience. Multiproto > has been under development for some time and I know many of you have > been anxious for its arrival. I would also like to thank all the > people who've helped code and test the new api. Last but not least, a > thanks to the app developers who've supported multiproto, and whose > continued support is very much appreciated. > > As you might already know, I've been out-of-town for the last few > months and haven't been able to progress multiproto further. I've now > returned and am glad to announce I've been putting the finishing > touches on the multiproto api, along with many fixes/updates to > supported drivers. Multiproto has reached a state where it is ready > to be adopted into the kernel and already has a pull request to do so. > > Here are some important pieces of information for you to know: > > current supported modulations with supported hardware: > DVB-S, DVB-S2, DVB-T, DVB-C, DVB-H > > How big is multiproto? > It's not. It doesn't exceed the size of the legacy api and is infact > smaller when used in non-legacy mode. > > Does it support ISDB-T, ATSC-MH, CMMB, DBM-T/H? > Intentionally, no! Experience with the old api development has proven > that making blind assumptions about delivery systems is a bad idea. > It's better to add in support for these when the hardware actually arrives > and can be properly tested. There is enough reserved space in the api to > support future modulations. > > current supported chipsets/devices: > STB0899 based cards (AD SP400/VP-1041, TT S2 3200, KNC1 DVB-S2 etc.) > > drivers currently in development: > STB0900/STB0903 based (eg. SAA716x based cards: AD SE-200/VP-1028, etc.) > > To clear up some misinformation and misconceptions: > > Is multiproto backwards compatible with previously built binaries? > YES! You don't need to do anything to make it backward compatible. > > Does multiproto have support for drivers found in v4l? > YES! Multiproto includes the v4l tree as well. However, the software > you use must support the multiproto api in order to use them. > Fortunately many already do but in the event support for the api must > be added, it can usually be done with minor changes. > > Are new modulations possible? > YES! Multiproto has been designed so that adding new future > modulations may be done with minimal effort. This will help speed up > the driver development process and allow us to use this api for some > time to come. > > If you would like to use any of these drivers now, you may pull the > tree from http://jusst.de/hg/multiproto. Drivers may be configured > with 'make menuconfig' the same as you've done with v4l. > > Feedback, bug reports, etc. are welcomed and encouraged! Please feel > free to > contact me via email at: abraham.manu@xxxxxxxxx > > If you have an unsupported device, please let me know! > > Best Regards, > Manu _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
