Re: Re: ioctl parameters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Fri, 15 Feb 2002, Joe Burks wrote:
> I have to disagree, the API as published in not at all clear.  Here 
> is exactly what it says:
> 
> "Once the mmap has been made the VIDIOCMCAPTURE ioctl sets the image size you 
> wish to use (which should match or be below the initial query size). Having 
> done so it will begin capturing to the memory mapped buffer. Whenever a 
> buffer is "used" by the program it should called VIDIOCSYNC to free this 
> frame up and continue. to add:VIDIOCSYNC takes the frame number you are 
> freeing as its argument."

I think the problem here is the sentence, "Whenever a buffer is "used" by the
program it should called VIDIOCSYNC to free this frame up and continue."  Not
only does this not make sense, it isn't even grammatically correct!

I think what the author was trying to say, is that when the application wishes
to use or process the buffer that it gave to the driver with VIDIOCMCAPTURE,
the program should call VIDIOCSYNC so that the driver will give the buffer
back to the program.

"buffer is used" should instead be, "buffer will be used" 

"it should called" should instead be, "it should first call" 

"to free this frame and continue" should instead be, "to wait for the driver
to finish with the buffer."





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux