> The memory allocation should be done by the driver, because of the grabber dma.
Where is the problem? You can simply mmap the driver buffers. The v4l
interface does'nt limit the number of buffers provided by the driver.
current bttv version allow up to 64 buffers (the default is 2 buffers,
can be tweaked at insmod time).
> The application can dynamically change the ring buffer size and using
> ExcludeImgBufferFromAqu() it can keep several frames as long as needed.
Does'nt work yet, but will once we use the support for dma-to-userspace
(which is new in 2.4.x) in v4l it will work. You can simply malloc() your
buffers then.
> Synchronisation with Vsync could be done in a second application thread using
> poll().
poll() is'nt supported, but if you are using a extra thread anyway you can
simply use the VIDIOSYNC ioctl.
Gerd
--
Protecting the children is a good way to get a lot of adults who cant
stand up for themselves. -- seen in some sig on /.
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
