On Mon, 4 Aug 2003, Ronald Bultje wrote: >On Mon, 2003-08-04 at 10:18, Tuukka Toivonen wrote: >> please notice that this is BUGGY code. It doesn't work if the driver >> provides only one buffer (which is specifically allowed by the API docs). >I think it's valid behaviour for an application to expect/want more >buffers, too. GStreamer nicely errors out with a "we want at least two Why do you think so? API.html says "The number of frames supported is device dependent and may only be one" and the way my driver works, more than one buffer would be just waste of memory. My driver has workaround for buggy applications which emulates two buffers with just one by placing them into same memory address. But this feels a bit hackish (although I guess it's still V4L api compatible, at least as long as one doesn't _write_ to the mmap-buffer). Besides, it's trivial to fix applications IMHO. At least for Motion it was.
