Mauro doesn’t explain his reason for not wanting both. Also, the upstream driver is actively maintained. Reality is probably a bit more complex though. 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. It takes very little time to conduct a childish flamewar.
|Date Added:||6 March 2014|
|File Size:||15.47 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
EM28xx cards list — Linux Media Subsystem Documentation documentation
Posted Nov 11, At that time em8xx was no single binary driver available from my side anyway, everything em28xc always been opensource this also has to be considered. Markus Rechberger The sad story of the em28xx driver. 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.
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. Reality is em28cx a bit more complex though. The sad story of the em28xx driver Posted Nov 12, 6: Some time, some sociologist may want to use that material in a thesis about group dynamics in open source development Posted Nov 26, If someone looks at the audio driver, and the patches for the audio driver it’s the code I’ve written, bugfixes to read for the videoframes the same story but never taking into account all the devices which were supported by the em28xx driver which I worked on constantly.
As a user, it’s unbelievable to me that these guys have so much time on their hand for childish flamewars. 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. Both upstream and the 4 duplicated drivers have similar functionality. This review notwithstanding, Mauro has indicated that he is not interested in accepting this patch.
It can do some setup steps which the API currently cannot handle. Only after this effort was well underway did Markus begin developing yet another in-kernel driver. It also eventually lead to some nice code cleanups. Log in to post comments The sad story of the em28xx driver.
It’s all connected, including multiple flamewars.
Obviously, this hasn’t worked out very well in this instance. It takes very little time to conduct a childish flamewar. 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. 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 At that time nothing was a problem because there were only analog devices available.
And in most cases newer drivers support more hardware, not less.
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. This attempt to exercise control over freely-licensed code was slapped down by Andrew Morton and others, but it left unpleasant memories behind. Best would be lihux replace you as a maintainer since you don’t have any respect of others work either.
How to configure the Linux kernel/drivers/media/video/em28xx
The userspace driver attempt. Rather, a developer puts code into the mainline so that the whole rest of the world can maintain it. Someone could dig into the whole topic at least for a week fulltime.
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? Hans Verkuil The sad story of the em28xx driver.
Messages to me from Markus threatening to take his code closed-source if he didn’t get lniux way didn’t exactly encourage me to support it either. The sad truth would seem to be that, while working with the community is something that a couple thousand developers do with little trouble every year, there will always be a few who have difficulties.
Posted Nov 12, 6: