On Mon, 4 Aug 2003, Tuukka Toivonen wrote: > 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. If the application cannot read the buffer fast enough, and at exactly the proper time, it will either miss frames, or get corrupted frames. This my not be the fault of the application, it could be limited bus bandwidth, or disk latency if recording. > 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). This is not the proper way to fix it. And is more than a bit hackish. If an application requires more than one buffer, yo never want to lie and say you have more than one if you don't. > Besides, it's trivial to fix applications IMHO. At least for Motion it was. But maybe not so easy to fix everyones hardware. Ed Okerson
