Mauro doesn’t explain his reason for not wanting both. 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. The project is moreover looking for lower skilled people who can be taught what to do do it as A or B says otherwise they’ll run against C. 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. These changes were not popular in the Video4Linux community, and there were fears that they could break unrelated drivers.

Uploader: Moogusho
Date Added: 27 September 2018
File Size: 30.89 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 37498
Price: Free* [*Free Regsitration Required]

Only after this effort was well underway did Markus begin developing yet another in-kernel driver. The advantages of improving the current driver, rather than duplicating some of its functionality in a new code base, are clear. 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. So let’s start and add it here: Both upstream ek28xx the 4 duplicated drivers have similar functionality.

Of course, losing “authority” over code is inherent in releasing that code under a license like the GPL. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive.

So binary drivers here or there is basically the same. 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. 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.


In particular, users of the code — people with a material interest in it — maintain it. Posted Nov 20, It’s not a project for innovative people to work on own ideas that for other open operating systems are better in that case.

It has coding style and copyright attribution problems; a quick review has also left your editor wondering about locking issues.

eMPIA Technology

Please visit this page to dmpia up and keep LWN on the net. 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 more attention and tend to improve quickly.

At this time I faced the problem that the analog and digital TV framework was separated, and there was certainly also some flamewar going on between v4l and the dvb people.

There is no point really to rehash all the old stuff, and to blame person a or person epmia or person c.

There were code quality issues too, of course, but I’m not sure anyone got as far as looking at those. Building a virtual front between developers who actually supported linux for a long time isn’t healthy.

Multiple drivers are easily accepted as temporary solution, but then someone must merge support for other hardware – and then we have “reiserfs situation” where developer works for it’s own feature and against all others 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. That seems to be the opposite of the open source process. Markus Rechberger The sad story of the em28xx driver.


It’s a huge amount of work that no one wants to do and in this case with very little benefit. What we have here is a classic empiw of an wm28xx mismatch between a developer and the development community. The sad story of the em28xx driver Posted Nov 17, First of all let’s start at the beginning and not in the middle of everything.

All of these are weak. His efforts to enhance emlia 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.

CONFIG_VIDEO_EM28XX: Empia EM28xx USB video capture support

So the user-space approach, like its predecessor, was not merged. 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.

Only then would I be in favor of merging the empia driver. Now Markus is back with a driver that, to all appearances, duplicates the functionality of a driver which is already in the mainline kernel.

Reality is probably a bit more complex though.

The tone of the discussion is, perhaps, best seen from this note sent to Video4Linux maintainer Mauro Carvalho Chehab: