Multiple drivers are easily accepted as temporary solution, but then someone must merge support for other hardware – and then we have “reiserfs situation” where developer works for it’s own feature and against all others Subscriptions are the lifeblood of LWN. Until now I have seen no attempts to make these changes, alas. The sad story of the em28xx driver Posted Nov 12, 0: His efforts to enhance that driver quickly ran into trouble, though, when he tried to make substantial changes to the low-level tuner interface – changes which affected a number of other drivers. Meanwhile, the other developer added the main required feature support for hybrid analog-digital tuners to the Video4Linux code in roughly the same way as they’d proposed earlier, but written from scratch, and this was accepted. So, there’s no sense on accepting those duplicated drivers.
|Date Added:||7 November 2004|
|File Size:||57.56 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
When I once asked him about joining that stuff he just told me well but you have it already done.
Em28xx devices – LinuxTVWiki
Now one group the v4l group has taken over without taking other dvb people who managed the project before as a small group before By Mepia Corbet November 11, Over the last year or two, the kernel development process has been changed in a deliberate attempt to make the addition of new drivers easier.
Hans promised to work with the community on Reiserfs and so after long deliberation it was empiw in kernel. Eventually, Markus came back with a new approach which moved much of the tuner code into user space.
That seems to be the opposite of the open source process. The sad story of the em28xx driver Posted Nov 16, Let’s just agree that you guys disagreed, and move forward.
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. Posted Nov 17, Also, the upstream driver is actively maintained. Best would be to replace you as a maintainer since you don’t have any respect empa others work either.
The sad story of the em28xx driver
I never dropped off anyone contributing to that project, rather helped them to get further into it and the code authors as well as the support mailinglist are a proof of that. Multiple drivers are easily accepted as temporary solution, but then someone must merge support for other hardware – and then we have “reiserfs situation” where developer works for it’s own feature and against all others In response to this rejection, Markus claimed ownership of the em28xx driver and asked that it be removed from the mainline kernel.
Someone could dig into the whole topic at least for a week fulltime. But such problems are common to drivers which have spent a lot me28xx time out of tree; they are simply something to fix. There have been a couple of approaches to solve the technical problem to share 1 component between analog and digital TV the tuner back then.
empiz So one could make the case for merging the new driver and, eventually, removing the older one. Rather, a developer puts code into the mainline so that the whole rest of the world can maintain it. If there are technical reasons to have two drivers it’s Ok, but if the reasons are political Meanwhile, this driver contains the result of years of work and access to the relevant data sheets; freezing it out may not be in the best interests of kernel developers or users.
Posted Nov 15, 5: His efforts to enhance that driver quickly ran into trouble, though, when he tried to make substantial changes to the low-level tuner interface – changes which affected a number of other drivers.
Experience with drivers merged under this policy has generally been positive; once those drivers head for the mainline, em28zx get more attention and tend to improve quickly. So the user-space approach, like its predecessor, was not merged. So I think your real objection isn’t to the developers’ allocation of their time, but to ejpia way they choose to conduct their lives.
So it is not entirely surprising that this driver has not been received with a great deal of enthusiasm. If someone looks at the audio driver, and the patches for the audio driver it’s the code I’ve written, bugfixes to read for the em;ia the same story but never taking into account all the devices which were supported by the em28xx driver which I worked on constantly.
EM28xx cards list — Linux Media Subsystem Documentation documentation
Log in to post comments The sad story of the em28xx driver. So binary drivers here or there is basically the same. I can think of another drawback: Posted Smpia 27, What we have here is a classic story of an impedance mismatch between a developer and the development community.
As a user, it’s unbelievable to me that empix guys have so much time on their hand for childish flamewars. 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. At the beginning of hybrid devices came up and I continued to work on the driver.