The userspace drivers used a couple of self written drivers. 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. The sad story of the em28xx driver Posted Nov 12, 6: This one also seemed to fail to meet kernel code quality standards last time I checked, mainly due to incorporating large chunks of third-party code. 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.

Uploader: Voodoozil
Date Added: 3 February 2014
File Size: 67.8 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 40754
Price: Free* [*Free Regsitration Required]

Both upstream and the 4 duplicated drivers have similar functionality. So it is not entirely surprising that this driver has not been received with a great deal of enthusiasm. Kernel em28x are quite reluctant to include driver which works on subset of hardware just because driver developer is not interested with community work. The sad story of the em28xx driver Posted Nov 13, 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.

So in order to avoid that someone has to disallow the usbfs and i2c-dev interface. ej28xx

This made inclusion of reiser4 more-or-less impossible: So now the userspace stuff comes in thinking about how to open up that project again so that work can be used with em28cx existing kernel. While Markus was working on his own version of the code, others were putting patches into the mainline em28xx driver.


Markus The sad story of the em28xx driver.

EM28xx cards list — Linux Media Subsystem Documentation documentation

But such problems are common to drivers which have spent a lot of time out of tree; they are simply something to fix. 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 ; em28xs of them proposed a simple change that would add better backwards compatibility, but Markus basically said “take it as it is or leave it”.

Hans promised to work with the community on Reiserfs and so after long deliberation it was included in kernel. So one could make the case for merging the new driver and, eventually, removing the older one.

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. Posted Nov 24, 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 em82xx to the user.

Another point here could be what is a kernelspace driver worth which requires firmware and doesn’t come with firmware. That seems to be the opposite of the open source process. Posted Nov 13, 1: He then continued development of the code, hosting it on his own server.

em28xx – Ubuntu Wiki

Posted Nov 12, 9: The userspace drivers used a couple of self written drivers. It has coding style and copyright attribution problems; a quick review has also left your editor wondering about locking issues. We got video, tuning and audio work.


Also quite a few bugs have been fixed in the kernelframework eg tuner-core it cost alot time all together and the work didn’t get valued at all. Posted Nov 14, Em28sx efforts to enhance that driver quickly ran into trouble, though, when he tried to make substantial changes to em2x8x low-level tuner interface – changes which affected a number of other drivers.

By Jonathan Corbet November 11, Can’t a higher-up maintainer intervene?

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

They fight for at least three years now and they still don’t have a useful infrastructure to support DVB-S2 devices. I got around i2c-dev which em28xz the access of those shared components in userland, the only outstanding gap in order to remain compatible with existing tv apps was to add a small wrapper to resubmit the controls to userspace sick isn’t it?

The advantages of improving the current driver, rather than duplicating some of its functionality in a new code base, are clear. The article mentions the confusion factor of having two em28x drivers.

Best would be to replace you as a maintainer since you don’t have any respect of others work either.