In this case it’s bloody disgusting that code was put on the backburner in favour of waiting for somebody else to complete their alternative solution just because A liked B better than C. These changes were not popular in the Video4Linux community, and there were fears that they could break unrelated drivers. Building a virtual front between developers who actually supported linux for a long time isn’t healthy. 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. If the code doesn’t get maintained and becomes unusable, we just drop it back out. Posted Nov 24,

Uploader: Aralabar
Date Added: 9 June 2004
File Size: 69.39 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 48071
Price: Free* [*Free Regsitration Required]

In such cases, the long-term goal is usually to work toward the removal of one of the drivers. The sad sm28xx of the em28xx driver Posted Nov 24, Markus The sad story of the em28xx driver. The sad story of the em28xx driver Posted Nov 12, 9: This review notwithstanding, Mauro has indicated that he is not interested in accepting this patch.

Of course, losing “authority” over code is inherent in releasing that code under a license like the GPL. It’s same as with Reiser4 Posted Nov 12, 9: We got video, tuning and audio work. There are users who will attest that the drivers work, and that Markus provides good support for them.

kernel: add video-em28xx module (c) · Commits · Turris / openwrt · GitLab

At times, Markus tried to block those changes. 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.


Jonathan’s article is overall ok, but it starts right after the bad things happened when the mood of everyone was already below something good. Some time, some sociologist may want to use that material in a thesis about group dynamics in open source development Let’s just agree that you guys disagreed, and move forward.

There was some prolonged feuding relating to changes to the core code. It’s might empiaa 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. The drivers which everything was about are still not available in the kernel, it basically was about Micronas chips back then.

If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Markus was one of the authors of the original em28xx driver, first merged for the 2. The project is moreover looking for lower skilled people who can be emoia what to do do it as A or B me28xx otherwise they’ll run against C. Meanwhile, this fm28xx contains the result of years of ej28xx and access to the relevant data sheets; freezing em28sx out may not be in the best interests of kernel developers or users.

Can’t a higher-up maintainer intervene? If you are abusing developers’s and users’s trust it becomes suddenly much harder to integrate code in kernel.

At that time empix was a problem because there were only analog devices available. 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.


The sad story of the em28xx driver Posted Nov 12, 0: But such problems are common to drivers which have spent a lot of time out of tree; they are simply something to fix.

The sad story of the em28xx driver

The fact that Markus clearly intended to have some dm28xx that code appear in the form of binary-only blobs did not help his case. It could easily be that this was mistaken though. Here we have again one guy against a supposed “clique” of kernel developers.

It’s same as with Reiser4. The sad story of the em28xx driver Posted Nov 17, 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.

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.

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.