Markus was one of the authors of the original em28xx driver, first merged for the 2. In such cases, the long-term goal is usually to work toward the removal of one of the drivers. Both upstream and the 4 duplicated drivers have similar functionality. Posted Nov 24, Someone could dig into the whole topic at least for a week fulltime. So I think your real objection isn’t to the developers’ allocation of their time, but to the way they choose to conduct their lives. We got video, tuning and audio work.

Uploader: Kilrajas
Date Added: 28 March 2007
File Size: 59.19 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 17373
Price: Free* [*Free Regsitration Required]

So at that point there was already a large codebase depending on it, and a merge request has been sent. It’s same as with Reiser4 Posted Nov 14, The advantages of improving the current driver, rather than duplicating some of its functionality in a new code base, are clear. There are users who will attest that the drivers work, and that Markus provides good support for them.

EM28xx cards list — Linux Media Subsystem Documentation documentation

In short, Markus has been told to go away until he is prepared to submit his work in the form of a series of small patches to the in-tree em28xx driver. Posted Nov 26, On the other hand, video developer Hans Verkuil reviewed the new driver and concluded: This review notwithstanding, Mauro has indicated that he ej28xx not interested in accepting this patch.

It’s not a project for innovative people to work on own ideas that for other open operating systems are better in that case.


The sad em28cx of the em28xx driver Posted Nov 13, So in order to avoid that someone has to disallow the usbfs and i2c-dev interface. Messages to me from Markus threatening to take his code closed-source if he didn’t get his way didn’t exactly encourage me to support it either. Now one group the v4l group has taken over without taking other dvb people who managed the project before as a small group before Experience with drivers merged under this policy has generally been positive; once those drivers head for the mainline, they get e,28xx attention and tend to improve quickly.

Basically there are too many good people involved already.

Posted Nov 27, This will be my last comment about em28x unless someone starts to em2x8x clear about the whole situation. The sad story of the em28xx driver Posted Nov 27, The sad truth would seem to be that, while working with the community is something that me28xx couple thousand developers do with little trouble every year, there will always be a few who have difficulties.

The tone of the discussion is, perhaps, best seen from this note sent to Video4Linux maintainer Mauro Carvalho Chehab: Posted Nov 12, It’s same as with Reiser4 Posted Nov 15, 5: Posted Nov 15, 5: If you appreciate our content, please buy a subscription and make the next set of articles possible.

What we have here is a classic story of an impedance mismatch between a developer and the development community.


So this code was not merged. Both upstream and the 4 duplicated drivers have similar functionality.

The sad story of the em28xx driver

Building a virtual front between developers who actually supported linux for a long time isn’t healthy. Hans promised to work with the community on Reiserfs and so after long deliberation it was included in kernel.

The sad story of the em28xx driver Posted Nov 12, This driver works with a number of video acquisition devices based on Empia chips; many of those are not supported en28xx the kernel now. So let’s start and add it here: After few years he started to close bugs and feature requests with “use reiser4” effectively abandoning users and stopped reiserfs support when something went emm28xx 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.

This was one possibility yes, but I also pointed out that the already available i2c-dev infrastructure could directly be used with the driver for setting up chips. If there are technical reasons to have two drivers it’s Ok, but if the reasons are political Only after this effort was well underway did Markus begin developing yet another in-kernel driver.