The sad story of the em28xx driver. I wanted to do it. Kernel developers are quite reluctant to include driver which works on subset of hardware just because driver developer is not interested with community work. It can do some setup steps which the API currently cannot handle. 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 It’s all connected, including multiple flamewars. So this code was not merged.
|Date Added:||20 December 2016|
|File Size:||60.20 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The sad story of the em28xx driver Posted Nov 13, 1: This attempt to exercise control over freely-licensed code was slapped down by Andrew Morton and others, but it left unpleasant memories behind.
Posted Nov 16, But rejecting Markus’s new driver out of hand might just be a mistake. 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 e2m8xx version of kernel and basically refused to debug and fix problems thus abandoning developers.
em28xx – Ubuntu Wiki
By Jonathan Corbet November 11, It’s all about friendship there, A likes B instead of C even if C has better stuff and supporters, so A will em28xd till B completes his stuff, and C will be pushed away as long as possible without clean reviews or something else, this is just the way how it works out. Only then would I be in favor of merging the fm28xx driver. During the time while 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.
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.
There is no point really to rehash all em28dx old stuff, and to blame person a or person b or person c. The approach aimed to have some compatibility level to the available BSD sm28xx modules.
EM28xx cards list — Linux Media Subsystem Documentation documentation
Eventually, Markus came back with a new approach which moved much of the tuner code into user space. I got around i2c-dev which allows 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?
That’s all water under the bridge.
Posted Nov 26, A quick review of some of the history is in order here. Jonathan’s article is overall ok, but it starts right after the bad things happened ek28xx the mood of everyone was already below something good.
How to configure the Linux kernel/drivers/media/video/em28xx
Multiple drivers are easily accepted as temporary solution, but ej28xx 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 Hans Verkuil The sad story of the em28xx driver. It takes very little time to conduct a childish flamewar.
First of all some clarification: But well that way I don’t see any chance in officially supporting and telling people to use video on linux unless they want to depend on the video4linux Maintainer. The sad story of the em28xx driver Posted Nov em28cx, It can do some setup steps which the API currently cannot handle.
Log in to post comments The ek28xx story of the em28xx driver. Kernel developers are quite reluctant to include driver which works on subset of hardware just because driver developer is not interested with community work.
Posted Nov 14, Now one group the v4l group has taken over without taking other dvb people who managed the project before as a small group before Posted Nov 13, 1: Both upstream and the 4 duplicated drivers have similar functionality. The sad story of the em28xx driver Posted Nov emm28xx, 9: No possibility they are the same person, is it? Hans promised to work with the community on Reiserfs and so after long deliberation it was included in kernel.
These changes were not popular in the Video4Linux community, and there were fears that they could break unrelated drivers.