It can do some setup steps which the API currently cannot handle. Posted Nov 26, Posted Nov 12, 0: It’s a huge amount of work that no one wants to do and in this case with very little benefit. By Jonathan Corbet November 11, Some time, some sociologist may want to use that material in a thesis about group dynamics in open source development

Uploader: Bajin
Date Added: 14 December 2013
File Size: 51.19 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 57109
Price: Free* [*Free Regsitration Required]

So binary drivers here or there is basically the same. In the process, this long story has helped to give the Video4Linux development community a bit of a reputation as a dysfunctional family – a perception which those developers e28xx only now beginning to overcome. Please sign up today! At that stage device node locking, preventing dvb appications to use the nodes while analog TV was in use was already implemented, and I also worked out alot other PCI devices some are still not merged with mainline.

Posted Nov 26, As a user, it’s unbelievable to me that these guys have so much time on their hand for childish flamewars. Another point here could be what is a kernelspace driver worth which requires firmware and doesn’t come with firmware. Back then Greg Kroah pointed out that binary drivers could use that interface, it was accepted because he basically didn’t clash with another developer.

Just one, I have to write that Michael Krufky was also involved into why it turned bad. Eventually, Markus came back with a lniux approach which moved much of the tuner code into user space.

So in order to avoid that someone has to disallow the usbfs and i2c-dev linuxx. Now continue reading with the article ontop of it.


The sad story of the em28xx driver

They ended with Markus submitting some code which made non-backwards compatible changes to that code something some of the other developers didn’t like ; one of them proposed a simple change that would add better backwards compatibility, e,28xx Markus basically said “take it as it is or leave it”.

I agree with Jonathan that many things finally went that way BUT there’s en28xx kind of reason for it. Is it actually a requirement for driver inclusion that future support be lined up? As an Empia Technology employee, Markus has access to the relevant data sheets and is, thus, well placed to write a fully-functional driver.

That’s all water under the bridge. Rather, a developer puts code into the mainline so that the whole rest of the world can maintain it.

The drivers which everything was about are still not available in the kernel, it basically was about Micronas chips back then. Posted Nov 13, After few years he started to close bugs and feature requests 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.

Only then would I be in favor of merging the empia driver. They fight for at least three years now and they still don’t have a useful infrastructure to support DVB-S2 devices.

Log linuc to post comments The sad story of the em28xx driver. Best would be to replace you as a maintainer since you don’t have any respect of others work either.


EM28xx cards list — The Linux Kernel documentation

There is no point really to rehash all the old stuff, and to blame person a or person b or person c. Em228xx whole issues at that time gave him the opportunity to work on his own stuff even more to let the existing em28xx code left behind. 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 sm28xx depending on it, and a merge request has been sent. Posted Nov 12, It’s about that this code has been lijux for years http: There was even a period where the code was relicensed to the MPL, apparently as part of an attempt to prevent it from being taken into the mainline.

In such linus, the long-term goal is usually to work toward the removal of one of the drivers. Ok I acknowledge that is what’s wanted and how it should be done. There are users who will attest that the drivers work, and that Markus provides good support for them. While Markus was working on his own version of the code, others were putting patches into the mainline em28xx driver. At that time there was no single binary driver available from my side anyway, everything has always been opensource this also has to be considered.