Manu, On Wed, 24 Sep 2008, Manu Abraham wrote: > Mauro Carvalho Chehab wrote: > [..] >> The main arguments in favor of S2API over Multiproto are: >> > > [..] > >> - Capability of allowing improvements even on the existing standards, >> like allowing diversity control that starts to appear on newer DVB >> devices. > > > I just heard from Patrick, what he meant by this at the meeting and the > reason why he voted for S2API, due to a fact that he was convinced > incorrectly. Multiproto _already_has_ this implementation, while it is > non-existant in S2API. In order to not have people getting me wrong here, I'm stating now in public: 1) I like the idea of having diversity optionally controlled by the application. 2) My vote for S2API is final. It is final, because the S2API is mainly affecting include/linux/dvb/frontend.h to add user-API support for new standards. I prefer the user-API of S2API over the one of multiproto because of 1). All the other things around multiproto are dvb-core/dvb_frontend internal. They have no relation with the user-interface. This I understood during the BOF, the microconf and the numberless talks we had around LPC. Manu, it would be extremely good to have your modifications of dvb-core/dvb_frontend within the 4 weeks schedule in order to have the maximum number of hardware supported by that time. If you do not have the time to do that right now, I'm sure people are willing to help. However - we can always change dvb_frontend/dvb-core internals at any time without breaking the user-interface. best regards, Patrick. _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
