On Wed, 2017-01-25 at 10:09 -0800, Michael Zoran wrote: > On Wed, 2017-01-25 at 18:39 +0100, Stefan Wahren wrote: > > > Michael Zoran <mzoran@xxxxxxxxxxxx> hat am 25. Januar 2017 um > > > 17:53 > > > geschrieben: > > Looking at the TODO shows 3 candidates: vc_mem, bcm2835-camera, > > VCSM > > > > I suggest to pick one first, because the kernel developer for > > bcm2835 > > are limited. So my favorite would be bcm2835-camera, since it's the > > only driver with a practical application for a non-developer. > > > > @Michael: Does this make sense to you? > > This isn't my decision. > > But I'm a personal fan of bcm2835-audio. I know it isn't on the TODO > list, but it was the reason I started down this path in the first > place. > > Eric is working on a replacement for it, but I'm not sure when he > will > have it available. > So I'm looking at the camera driver and it would again be starting with a very large driver. It's 7000+ lines of code. On the other hand, the audio driver is only 2500 lines and much of it could be simplified. Eric's hdmi audio driver is certainly the better way to go, but it has many issues that need to be addressed as well. Ranging from legal(the encoding for HDMI audio is an ancient closed standard even through an open source solution is available and it's a very simple standard) ranging to architectural such as you can't have floating point in kernel drivers for something as simple as the volume control. I would probably even be willing to submit the initial version of the audio driver to staging and yes I would cleanup most of the checkpatch.pl issues on the initial patch. But if people want to hit the nuke button on vc04_services, that's certainly an option and it's not my decision. I'm not the owner of the kernel source tree... _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
