Re: VIDIOC_ENUM_FRAMESIZES in linux_ioctl.c

2013-01-13 Thread Markiyan Kushnir
On 13.01.2013 18:48, Juergen Lock wrote: On Sun, Jan 13, 2013 at 06:11:13PM +0200, Markiyan Kushnir wrote: Hi, Any reason why LINUX_VIDIOC_ENUM_FRAMESIZES, LINUX_VIDIOC_ENUM_FRAMEINTERVALS, LINUX_VIDIOC_ENCODER_CMD, and LINUX_VIDIOC_TRY_ENCODER_CMD in compat/linux/linux_ioctl.c have been put un

Re: VIDIOC_ENUM_FRAMESIZES in linux_ioctl.c

2013-01-13 Thread Juergen Lock
On Sun, Jan 13, 2013 at 06:11:13PM +0200, Markiyan Kushnir wrote: > Hi, > > Any reason why LINUX_VIDIOC_ENUM_FRAMESIZES, > LINUX_VIDIOC_ENUM_FRAMEINTERVALS, LINUX_VIDIOC_ENCODER_CMD, and > LINUX_VIDIOC_TRY_ENCODER_CMD in compat/linux/linux_ioctl.c have been put > under #ifdef VIDIOC_ENUM_FRAMES

VIDIOC_ENUM_FRAMESIZES in linux_ioctl.c

2013-01-13 Thread Markiyan Kushnir
Hi, Any reason why LINUX_VIDIOC_ENUM_FRAMESIZES, LINUX_VIDIOC_ENUM_FRAMEINTERVALS, LINUX_VIDIOC_ENCODER_CMD, and LINUX_VIDIOC_TRY_ENCODER_CMD in compat/linux/linux_ioctl.c have been put under #ifdef VIDIOC_ENUM_FRAMESIZES (looks like it's been there since rev. 221426, when the v4l2 support wa