hi johannes, --snip-- > > BTW, I don't claim to be right on my interpretation of the > DVB-S2 spec, however as long as we can't agree (i.e. > no one can give a good explanation why his version > of the DVB-S2 API is the correct one, and *everyone* > can agree on it), I think the while DVB-S2 API is useless. > > > I also say it again: I am deeply dissatisfied that none > of the people you mentioned at the bottom of > http://linuxtv.org/pipermail/linux-dvb/2006-May/010076.html > seem to care enough to participate in the discussion. > (Not to mention that app developers also don't > seem to care -- after all these are the ones who'll have > to deal with the new API.) > > Maybe we should just put the API change off for now. :-( no, we shouldn't. when i first started the discussion together with felix domke, rainer scherg ... i presented my very small part patch. it was just (pasted old ml stuff here) -------------------------------------------------------------------------------------------- On Tue, Nov 22, 2005, Marcel Siegert wrote: hi, as dvb-s2 will come along shortly we should be prepared. this is a first patch within a series that will appear to support dvb-s2 within the different apis. it just adds the new fec modes and the dvb-s2 rollflag enums. -------------------------------------------------------------------------------------------- there came a slightly answer: So far so good, but we should IMHO not commit partial solutions. I think we should bang out the complete API, with the part which Felix mentions in his posting. and commit it as one API change. Johannes -------------------------------------------------------------------------------------------- so, what should i say? we started nearly 6 (SIX!) month ago to discuss what we need for DVB-S2 support. result? we do know we need some new FEC modes and also the ROLLOFF flag. (even if that is only queried from the frontend) so what should we do now? dig at a nov.2005 created grave, just fetch my old patch to start over from scratch? split manus patch up into 20 small ones and maybe find out in another 5 to 6 month, that we need them all? i personally did about iirc 6 attempts to bring dvb-s2 into the api including several changes due to discussions. ok, maybe (and as i do think nowadays) my first thoughts were also a bit wrong, or i have been toooo optimistic to solve this in a short and simple way. the more i investigated on this topic, the more i posted, it became clearer to me, that is is _not_ just a DVB-S and different modulation. but instead of having some real constructive critics ( i do not call you on this, johannes :) ) we were talking about 3 weeks about how to name a paremeter struct or ioctl. of course, FE_SET_FRONTEND_NEW is fine, but what about FE_SET_FRONTEND_NEW_NEW next time? thats when i went into some regression. manu came up with his multiprotocol patch, and i realised that my concern is integrated. so i stopped developing my stuff. manu is actually writing a dvb-s2 driver, has got specs and is talking (yes on irc) to different people about their thinking of the patch. frequently there are suggestions/discussions and some pastebin's for different solutions. but these came all out of technical not naming issues. we all should concentrate on what we really want. that should be DVB not feeding google or any other kind of search engine with endless mailing list threads Result 1 - 10 of 911 für linuxtv multi protocol. on google today 14:44. no more comments. go for it ( maybe adjusted in some small pieces ) or wait until we have some individual solutions that already do appear are brought to the universe. everybody needs to have a special kernel patch for applying a patch that a special application patch recommends. thats MUCH more ugly than having _maybe_ 2 or 3 unneeded enum structs within the api interface. but thats just my opinion. i don't know if anyone counts on it. best regards marcel > > Johannes > > _______________________________________________ > > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
