By admin on March 3, 2020 0 Comments

Given that, one might well wonder why Markus Rechberger’s recently submitted “empia” driver series is encountering so much resistance. Hans Verkuil The sad story of the em28xx driver. This is, also, the way that kernel developers are normally expected to do their work. Posted Nov 14, It could easily be that this was mistaken though.

Uploader: Kazralkree
Date Added: 6 November 2017
File Size: 33.34 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 49719
Price: Free* [*Free Regsitration Required]

CONFIG_VIDEO_EM28XX: Empia EM28xx USB video capture support

In response to this rejection, Markus claimed ownership of the em28xx driver and asked that it be removed from the mainline kernel. During the time em28xxx 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.

Just one, I have to write that Michael Krufky was also involved into why it turned bad. Posted Nov 17, 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 are only now beginning to overcome.

How to configure the Linux kernel/drivers/media/video/em28xx

If there are technical reasons to have two drivers it’s Ok, but if the reasons are political 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. There were code quality issues too, of course, but I’m not sure em8xx got as far as looking at those. sm28xx


It’s same as with Reiser4 Posted Nov 15, 5: The approach aimed to have some compatibility level to the available BSD tuning modules. This review notwithstanding, Mauro has indicated that he is not interested in accepting this patch.

In particular, users of the code — people with a material interest in it — maintain it. All of these are weak.

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.

At times, Markus tried to block those changes. So the user-space approach, like its predecessor, was not merged.

em28xx – Ubuntu Wiki

Building a virtual front between developers who actually supported linux for a long time isn’t healthy. The sad truth would seem to be that, while working with the community is something that a couple thousand developers do with little trouble every year, there will always be a few who have difficulties.

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. By Jonathan Corbet November 11, Posted Nov 24, 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. Posted Nov 12, 0: Posted Nov 12, 9: The sad emm28xx of the em28xx driver Posted Nov 17, Markus The sad story of the em28xx driver.


Linux source code: drivers/media/video/em28xx/em28xx-video.c (v) – Bootlin

There seems to be little doubt that it has developed well beyond the in-tree driver; it supports a wider range of devices. Reality is probably a bit more complex though.

There was even a period where em28xz code was relicensed to the MPL, apparently as part of an linix to prevent liunx from being taken into the mainline.

It’s same as with Reiser4 Posted Nov 14, 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.

Posted Nov 26, Now one group the v4l group has taken over without taking other dvb people who managed the project before as a small group before The sad story of the em28xx driver Posted Nov 13, 1: 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, but Markus basically said “take it as it is or leave it”.