Dave Schmitz wrote:

> James Amendolagine wrote:
>
> > OK, I'm now using the
> >
> > ioctl(vf, VIDIOCSYNC, &j);
> >
> > call to block while v4l is finished writing the mmap. The error was
> > reporting that the device was busy. I still don't know how to get the
> > information about the window size though.
> >
> > Jamie
>
> Hey Jamie...
>
> Not sure if this is really the answer you're looking for but anyway.....
>
> If you do a..
>    struct video_capability  videoCapability;
>    ioctl(_videoDevice, VIDIOCGCAP, &videoCapability)
>
> and look at...
>   videoCapability.minwidth
>   videoCapability.minheight
>   videoCapability.maxwidth
>   videoCapability.maxheight
>

Those work for maximum sizes, but what happens if I ask for a 256x256 image?
If the hardware supports it, then it will be OK, but if it doesn't, it looks
like v4l tries to return something which is close, but I can't figure out
how to determine what size it selected.


>
> This will tell you the min/max capture sizes of the card... Based on that
> info you know the info for a correct call to..
>    struct video_mmap videoMmap;
>    ioctl(_videoDevice,  VIDIOCMCAPTURE, &videoMmap)
>
> Hope this helps...
>
> Cheers,
>
>  -Smity
>
> --
>    _____________________________________________________________________
>    * PULL-THE-PLUG, SLICE THE PIE: A fantasy in which offspring mentally
>      tallies up the net worth of his parents.
>           _____________________________________________________
>            Dave Schmitz            Interact-TV
>            [EMAIL PROTECTED]  http://www.interact-tv.com
>            Ph: 720.406.9399        Fax: 720.406.8424
>
> _______________________________________________
> Video4linux-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/video4linux-list



_______________________________________________
Video4linux-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/video4linux-list

Reply via email to