Markus Rechberger wrote: > As from my side I don't have the time to do a major rewrite or doing > some reordering again, please try to make the best out of what's > available now. > > The patches include more than 9000 lines of codechanges through the > v4l and dvb framework, these changes have been done during the last 1 > 1/2 years of split development from the main v4l-dvb code, I know it's > alot but it's worth to get it done now. It's not only about adding > support for one new device only. I know we've been over this, but I need to state my feelings on the matter, otherwise I would have to simply keep quiet, and that doesn't help the situation for anybody. I _strongly_ feel that the core changes being proposed here will hurt the integrity of the dvb subsystem. The main arguments for accepting these changes is that it "adds support for over 60 devices" and that the author "doesn't have any more time to spend on this." The argument currently on the table, is that these changes get merged now, and we fix any problems later. I feel that this sets a bad president. Who is to stop the NEXT developer from changing around the subsystem core against the desires of those developers actively maintaining the project? We have an established internal API, and developers should keep subsystem codingstyle intact. If we merge this now, who is to say that we will _ever_ get around to 'fixing' it? We are having enough problems as it is trying to agree on a way to merge the xc3028 driver into the kernel -- how will we ever agree on the 'fixup' method later? The answer is simple -- we'll never agree. What does this mean? It means that we have to compromise. The ability to compromise is very important when more than one person is working on a project. Heck, the word 'compromise' always comes up when people talk about marriage, living situations, etc. It also applies to discussions such as this. Again, as I understand, the most significant argument for pushing this in, is to finally get driver support for these sixty some-odd devices into the kernel. Please keep in mind that we're talking about a single tuner ic (xc3028) and the sixty devices that depend on the presence of the xc3028 driver. We _are_ talking about a single device (ic). Even still, if the priority is to merge support for the xc3028 tuner ic into the kernel in the quickest way possible, then there is a _much_ lesser evil available as an option. I do frown upon code duplication, however, in this case it is a safer alternative to the one currently on the table. Earlier versions of the xc3028 tuner driver were bound to the video4linux tuner.ko module, for the sake of tuning analog television stations. There was a wrapper present inside the em2880-dvb driver that allowed the dvb subsystem to access the xc3028 via tuner.ko. I am not a big fan of this solution, however, it does not touch any core subsystem code. DVB-only devices can use a separate module in order to access the xc3028 without imposing dependencies on the v4l core. I have already written such a module, based on Markus' work, and it has already been proven in the field as a working solution. see xc3028-fe.c in: http://www.linuxtv.org/~mkrufky/xc-bluebird.patch The only argument against this method, is that it requires some code duplication -- two drivers for the xc3028. One for analog via the v4l subsystem, the other for dvb via the dvb subsystem. I repeat -- I am NOT promoting code duplication, however, given the circumstances, and the fact that the reason for all the controversy is that people want the xc3028 driver merged into the kernel asap, this solution is truly the lesser of two evils. We already have some code duplicated for simple pll's such as the fmd1216me and lgh06xf tuners -- the only difference is the size of the code. If we decide to go this route, it will truly be the best compromise -- It will allow us to merge in support for the sixty some-odd devices that Markus is talking about, and it will allow for easy development of newer devices that use this tuner ic. The major benefit of this method is that it _will_ allow for us developers to put our heads together after the fact, and find better ways of supporting hybrid tuners. At that point, the pressure of 'trying to merge support for sixty devices' will be gone. Developers will finally be able to discuss this issue without the pressure of the current pending issues, and we _will_ be able to find a better solution. As far as I can tell, it seems that this is the only way for us to push this through, while not upsetting other developers. However, I must repeat that following my proposal does create a maintenance problem -- It means that any changes to the xc3028-tuner module will have to be carried over to the xc3028-fe module. Once the two modules get merged, however, it will become more apparent to developers as to the reasons why we need a better solution. I do believe that this will be a catalyst to discovering a proper solution later on. If we decide to go this route, then I will volunteer to keep up the maintenance of the xc3028-fe module until that proper, better solution is agreed upon. Regards, Michael Krufky _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
