On Friday 18 August 2006 15:19, Bill Davidsen wrote: > > Don't take it personally, just write working code people can patch in. > When your code has the features you mentioned it will be highly useful > and hopefully ported to many devices. I guess security monitoring is an > "industrial image processing application," which interests me. At the > moment I would call it an impressive proof of concept, but you have many > useful ideas for its future. I am not offended at all, I certainly agree with Pavel's opinion of 'do not invent new interfaces needlessly'. But this is a use case significantly different from what the v4l2 api is aimed at. As I wrote earlier, if it were not for other reasons, then changing the API is not an option because the software already ships. I can place the driver somewhere else in the kernel tree. I can fix any issues that someone may find with it. I certainly cannot replace it with something entirely different. If it is rejected, my only option is to submit the rest of the code, without the capturing driver (the platform is already in the kernel tree). Some may feel that a camera that cannot capture images is somewhat pointless, though... Of course, everyone is free to write a v4l2 driver, but will likely find that the hardware is not very suitable as a streaming video device. At least, it would be a very expensive one... Thomas -- Thomas Koeller, Software Development Basler Vision Technologies An der Strusbek 60-62 22926 Ahrensburg Germany Tel +49 (4102) 463-390 Fax +49 (4102) 463-46390 mailto:thomas.koeller@xxxxxxxxxxxxx http://www.baslerweb.com
