Posted Nov 17, While Markus was working on his own version of the code, others were putting patches into the mainline em28xx driver. I wanted to do it. Is it actually a requirement for driver inclusion that future support be lined up? 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. So this code was not merged. Posted Nov 27,
|Date Added:||18 January 2017|
|File Size:||62.14 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
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. It’s not a project for innovative people to work on own ideas that for other open operating systems are better in that case. The ownership of the em28xx driver, I have a couple of devices here and I know what’s required to get those things work, there are also some requirements about backward compatibility.
If the code doesn’t get maintained and becomes unusable, we just drop it back out. 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.
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. 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.
em28xx – Ubuntu Wiki
First of all let’s start at the beginning and not in the middle of everything. The tone of the discussion is, perhaps, best seen from this note sent to Video4Linux maintainer Mauro Carvalho Chehab: It has coding style and copyright attribution problems; a quick review has also left your editor wondering about locking issues. 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.
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. So at the end the code basically just got left behind and also during the development noone of those people who were against it was interested to join the core development – I asked several time on IRC, the ML posts didn’t get further anyway either.
How to configure the Linux kernel/drivers/media/video/em28xx
At times, Markus tried to block those changes. So in order to avoid that someone has to disallow rm28xx usbfs and i2c-dev interface. I can think of another drawback: In the end, some of the developers decided to just improve the version of the driver currently in-kernel rather than continuing to deal with Markus. Jonathan’s article is overall ok, but it starts right after the bad lihux happened when the mood of everyone was already below something good.
In this case it’s bloody disgusting that em8xx was put on the backburner in favour of waiting for somebody else to complete their alternative solution just because A liked B better than C. The approach aimed to have some compatibility level to the available BSD tuning modules.
Having multiple drivers for the same hardware in the kernel is not an ideal situation, but it is also not without precedent. The sad story of the em28xx driver Posted Nov 12, 0: The article mentions the confusion factor of having two similar drivers.
Linux source code: drivers/media/video/em28xx/em28xx-video.c (v) – Bootlin
The sad story of the em28xx driver Posted Nov 14, The sad story of the em28xx driver Posted Nov 13, 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 ; 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”.
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.
This driver works with a number of video lknux devices based on Empia chips; many of those are lniux supported by the kernel now. At this time I faced the problem that the analog and digital TV framework was separated, and there was en28xx also some e2m8xx going on between v4l and the dvb people. In my opinion it’s pretty much hopeless trying to convert the current em28xx driver into what you have.
My first approach was limited to a specific parameter setting which only allowed to receive some TV channels, I realized that and started over again digging further into the V4L and DVB framework. Is it actually a requirement for driver inclusion that future support be lined up? Em82xx whole issues at that time gave him the opportunity to work on his own stuff even more to let the existing em28xx code left behind. That’s non sequitur to me. Posted Nov 12, As an Empia Technology employee, Markus has access to the relevant data sheets and is, thus, well placed to write a fully-functional driver.
Markus The sad story of the em28xx driver.