It takes very little time to conduct a childish flamewar. While Markus was working on his own version of the code, others were putting patches into the mainline em28xx driver. In such cases, the long-term goal is usually to work toward the removal of one of the drivers. Log in to post comments The sad story of the em28xx driver. The fact that Markus clearly intended to have some of that code appear in the form of binary-only blobs did not help his case. During the time while working on it the driver already started supported more and more devices, and that small gap at the beginning became as a base for the entire code, everytime I tried to rework some bits in it it broke alot devices. Posted Nov 12,
|Date Added:||10 September 2007|
|File Size:||66.99 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The sad story of the em28xx driver
There are users who will attest that the drivers work, and that Markus provides good support for them. Subscriptions are the lifeblood of LWN. In the process, the new driver could receive some much-needed attention from other developers. Here we have again one guy against a supposed “clique” of kernel developers.
It would avoid the confusion which can come from having two drivers for the same hardware in the tree, and it would minimize the risk of losing important fixes which have been applied to the in-tree code. The ownership of the em28xx driver, I have a couple of devices here and I know what’s required to get those things work, there are also some requirements about backward compatibility.
So at that point there was already a large codebase depending on it, and a merge request has been sent. 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.
Posted Linuc 11, 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.
So it would seem that everybody’s interests are served by getting those drivers into the mainline tree. Markus Rechberger The sad story of the em28xx driver.
linkx First of all let’s start at the beginning and not in the middle of everything. It’s same as with Reiser4 Posted Nov 12, 9: This one also seemed to fail to meet kernel code quality standards last time Em82xx checked, mainly due to incorporating large chunks of third-party code.
Posted Nov 24, Posted Nov 17, Posted Nov 12, 0: Basically there are too many good people involved already. A quick review of some of the history is in order here. And in most cases newer drivers support more hardware, not less.
There was some prolonged feuding lonux to changes to the core code. Please visit this page to join up and keep LWN on the net.
Em28xx devices – LinuxTVWiki
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.
The sad story of the em28xx driver Posted Nov 17, Posted Nov 13, 1: The sad story of the em28xx driver Posted Nov 12, 6: So I think your real objection me28xx to llnux developers’ allocation of linx time, but to the way they choose to conduct their lives. Posted Nov 12, 9: Having multiple drivers for the same hardware in the kernel is not an ideal situation, but it is also not without precedent. It’s might be quite a problem for Linux as a platform when developers with such access to the hardware emm28xx as Markus can’t even properly contribute to the mainline kernel driver.
This made inclusion of reiser4 more-or-less impossible: Now one group the v4l group has taken over without taking other dvb people who managed the project before as a small group before I am sure the other people involved have their own recollections which may differ from your’s and memory fades, anyway. The sad story of the em28xx driver Posted Nov 11,