So now the userspace stuff comes in thinking about how to open up that project again so that work can be used with the existing kernel. 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. But rejecting Markus’s new driver out of hand might just be a mistake. Eventually, Markus came back with a new approach which moved much of the tuner code into user space. 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. In the process, the new driver could receive some much-needed attention from other developers.

Uploader: Fejind
Date Added: 26 April 2007
File Size: 41.4 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 82812
Price: Free* [*Free Regsitration Required]

There was some prolonged feuding relating to changes to the core code. It’s might be 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 sad story of the em28xx driver []

Another point here could empiw what is a kernelspace driver worth which requires firmware and doesn’t come with firmware. Posted Nov 13, The reason en28xx the big patch has always been that the code had to be rebased because the maintainer basically didn’t care about anything there. On the other hand, video developer Hans Verkuil reviewed the new driver and concluded: Posted Nov 14, Posted Nov 12, There have been a couple of approaches to solve eem28xx technical problem to share 1 component between analog and digital TV the tuner back then.


This review notwithstanding, Mauro has indicated that he is not interested in accepting this patch. 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 my opinion it’s pretty much hopeless trying to convert the current em28xx driver into what you have.

They ended with Markus submitting some code which made em288xx 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”. Is it actually a requirement for driver inclusion that future support be lined up? There were code quality issues too, of course, but I’m not sure anyone got as far as looking at those.

So at that point there was already a large codebase depending on it, and a merge request has been sent. 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. Messages to me from Markus threatening to take his code closed-source if he didn’t get his way didn’t exactly encourage emia to support it either.

They fight for at least three years now and they still don’t have a useful infrastructure to support DVB-S2 devices. The drivers which everything was about are still not available in the kernel, it basically was about Micronas chips back then.

As an Empia Technology employee, Markus has access to the relevant data sheets and is, thus, well placed to write a fully-functional driver. In this case it’s bloody disgusting that code was put on the backburner in favour of waiting em;ia somebody else to complete their alternative solution just because A liked B better than C.


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. And in most cases newer drivers support more hardware, not less. Same disagreements, same tone, same part of the kernel. Someone could dig into the whole topic at least for a week fulltime.

Posted Nov 12, 0: It is not hard to see this submission as an attempt to retake control of that eem28xx and, perhaps, restart the discussions from past years. Markus The sad story of the em28xx driver. Best would be to replace you as a maintainer since you don’t have any respect of others work either.

The sad story of the em28xx driver

First of all some clarification: Posted Nov 17, 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. What we have here is a classic story of an impedance mismatch between a developer and the development community.

He then continued development of the code, hosting it on his own server. The whole driver started at the end ofI started to reverse engineer the protocol and worked on it with Luca Risolia hope I got the name right.