Re: v4l2 api: supported resolution negotiation

2015-10-12 Thread Hans Verkuil
On 10/04/2015 08:49 PM, Sakari Ailus wrote: > On Sun, Oct 04, 2015 at 12:23:08PM +0300, Matwey V. Kornilov wrote: >> Hello, >> >> I learned from V2L2 API how to detect all supported formats using >> VIDIOC_ENUM_FMT. >> When I perform VIDIOC_S_FMT I don't know how to fill fmt.pix.width and >> fmt.pi

Re: v4l2 api: supported resolution negotiation

2015-10-04 Thread Nicolas Dufresne
Le dimanche 04 octobre 2015 à 21:49 +0300, Sakari Ailus a écrit : > I think the GStreamer > v4lsrc tries very small and very large values. The driver will clamp > them to > a supported values which are passed to the application from the > IOCTL. In GStreamer we try ENUM_FRAMESIZE, and when no supp

Re: v4l2 api: supported resolution negotiation

2015-10-04 Thread Sakari Ailus
On Sun, Oct 04, 2015 at 12:23:08PM +0300, Matwey V. Kornilov wrote: > Hello, > > I learned from V2L2 API how to detect all supported formats using > VIDIOC_ENUM_FMT. > When I perform VIDIOC_S_FMT I don't know how to fill fmt.pix.width and > fmt.pix.height, since I know only format. > How should I

v4l2 api: supported resolution negotiation

2015-10-04 Thread Matwey V. Kornilov
Hello, I learned from V2L2 API how to detect all supported formats using VIDIOC_ENUM_FMT. When I perform VIDIOC_S_FMT I don't know how to fill fmt.pix.width and fmt.pix.height, since I know only format. How should I negotiate device resolution? Could you point me? -- To unsubscribe from this list