Thomas Koeller wrote:
On Thursday 17 August 2006 17:31, Pavel Machek wrote:
Well, I guess v4l api will need to be improved, then. That is still
not a reason to introduce completely new api...
The API as implemented by the driver I submitted is very minimalistic,
because it is just a starting point. There's more to be added in future,
like controlling flashes, interfacing to line-scan cameras clocked by
incremental encodes attached to some conveyor, and other stuff which
is common in industrial image processing applications. You really do
not want to clutter the v4l2 API with these things; that would hardly
be an 'improvement'.
Different interfaces, designed to serve different purposes...
If you look at Pavel's posts WRT swsusp2, he has taken this position
before, that lack of functionality in {something} is no justification to
introduce a new solution, and that the limitations of {something} can be
addressed by incremental improvement. Like any good idea, this can be
carried to extremes.
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.
--
Bill Davidsen <davidsen@xxxxxxx>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
