I came up with the idea to refactor the tuner stuff in order to be able to use the same tuner code between both v4l and dvb, to make the story short this was declined. It is not hard to see this submission as an attempt to retake control of that driver and, perhaps, restart the discussions from past years. That’s non sequitur to me. Failure to merge it risks losing the work that has been done, and, perhaps, losing the future work of a developer who, for all his faults, is clearly trying to provide a better experience for Video4Linux users. The e and ee drivers had overlapping coverage for some time. It takes very little time to conduct a childish flamewar. In particular, users of the code — people with a material interest in it — maintain it.
|Date Added:||22 December 2011|
|File Size:||31.60 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I distinctly remember many devices having legacy as well as newer drivers supporting more devices, it does not hurt anybody to get his new driver in as an alternate driver and give the choice to the user. Posted Nov 12, 0: It’s might be quite a problem for Linux as a platform when developers with such access to the hardware specs as Markus can’t even properly contribute to the mainline kernel driver.
CONFIG_VIDEO_EM28XX: Empia EM28xx USB video capture support
This review notwithstanding, Mauro has indicated that he is not interested in accepting this patch. First of all let’s emia at the beginning and not in the middle of everything. It’s about that this code has been available for years http: The e and ee drivers had overlapping coverage for some time.
At this time I faced the problem that the analog and digital Empai framework was separated, and there was certainly also some flamewar going on between v4l and the dvb people.
Posted Nov 11, So I think your real objection isn’t to the developers’ allocation of their time, but to the way they choose to conduct their lives. In the end, some of the developers decided to just improve the version of the driver currently in-kernel rather than continuing to deal with Markus. They ended with Markus submitting some code which made non-backwards compatible changes to that empa something some of the other developers didn’t like ; one of them proposed a simple change that would add better backwards compatibility, but Markus basically said “take it as it is or leave empoa.
The sad story of the em28xx driver 
There was some prolonged feuding relating to changes to the core code. First of all some clarification: There was even a period ek28xx the code was relicensed to the MPL, apparently as part of an attempt to prevent it from being taken into the mainline. Only after this effort was well underway did Markus begin developing yet another in-kernel driver. So at that point there was already a large codebase depending on it, and a merge request has been sent. At the beginning of hybrid devices came up and I continued to work on the driver.
The sad story of the em28xx driver Posted Nov 17, So one could make the case for merging the new driver and, eventually, removing the older one.
There seems to be little doubt that it has developed well beyond the in-tree driver; it supports a wider range of devices. So it is not entirely surprising that this driver has not been received with a great deal of enthusiasm.
There is no point really to rehash all the old stuff, and to blame person a or person b or person c. My first approach was limited to a specific parameter setting which only allowed to receive some TV channels, I realized that and started over again digging further into the V4L and DVB framework.
Experience with drivers merged under this policy has generally been positive; once those drivers head for the mainline, they get more attention and tend to improve quickly. The approach aimed to have some compatibility level to the available BSD tuning modules. I don’t want to own the em28xx driver, I would like to maintain it since I did that for 3 years already, accepting useful patches giving reviews etc.
After few years he started to close bugs and feature em288xx with “use reiser4” effectively abandoning users and stopped reiserfs support when something went wring he pointed out that the same thing worked perfectly with previous version of kernel and basically refused to debug and fix problems thus abandoning developers.
Also quite a few bugs have been fixed in the kernelframework eg tuner-core it cost alot time all together and the work didn’t get valued at all. So let’s start and add it here: Is it actually a requirement for driver inclusion that future support be lined up? I got around i2c-dev which allows the access of those shared em28sx in userland, the only outstanding gap in order to remain compatible with existing tv apps was to add a small wrapper to resubmit the controls to userspace sick isn’t it?
I agree with Jonathan that many things finally went that way BUT there’s some kind of reason for it.
It’s same as with Reiser4 Posted Nov 12, 9: Posted Nov 20, The tone of the discussion is, perhaps, best seen from this note sent to Video4Linux maintainer Mauro Carvalho Chehab: It’s same as with Reiser4.