Re: [RFCv1 PATCH for v3.1] v4l2-ioctl: fix ENOTTY handling.

2011-08-09 Thread Hans Verkuil
On Tuesday, August 09, 2011 13:22:55 Mauro Carvalho Chehab wrote: > Em 09-08-2011 07:10, Hans Verkuil escreveu: > > On Sunday, July 31, 2011 14:43:44 Mauro Carvalho Chehab wrote: > >> Em 29-07-2011 09:10, Hans Verkuil escreveu: > >>> Hi all, > >>> > >>> While converting v4l2-compliance to correctly

Re: [RFCv1 PATCH for v3.1] v4l2-ioctl: fix ENOTTY handling.

2011-08-09 Thread Mauro Carvalho Chehab
Em 09-08-2011 07:10, Hans Verkuil escreveu: > On Sunday, July 31, 2011 14:43:44 Mauro Carvalho Chehab wrote: >> Em 29-07-2011 09:10, Hans Verkuil escreveu: >>> Hi all, >>> >>> While converting v4l2-compliance to correctly handle ENOTTY errors I found >>> several regressions in v4l2-ioctl.c: >>> >>>

Re: [RFCv1 PATCH for v3.1] v4l2-ioctl: fix ENOTTY handling.

2011-08-09 Thread Hans Verkuil
On Sunday, July 31, 2011 14:43:44 Mauro Carvalho Chehab wrote: > Em 29-07-2011 09:10, Hans Verkuil escreveu: > > Hi all, > > > > While converting v4l2-compliance to correctly handle ENOTTY errors I found > > several regressions in v4l2-ioctl.c: > > > > 1) VIDIOC_ENUM/G/S/TRY_FMT would return -ENO

Re: [RFCv1 PATCH for v3.1] v4l2-ioctl: fix ENOTTY handling.

2011-07-31 Thread Mauro Carvalho Chehab
Em 29-07-2011 09:10, Hans Verkuil escreveu: > Hi all, > > While converting v4l2-compliance to correctly handle ENOTTY errors I found > several regressions in v4l2-ioctl.c: > > 1) VIDIOC_ENUM/G/S/TRY_FMT would return -ENOTTY if the op for the particular >format type was not set, even though th

[RFCv1 PATCH for v3.1] v4l2-ioctl: fix ENOTTY handling.

2011-07-29 Thread Hans Verkuil
Hi all, While converting v4l2-compliance to correctly handle ENOTTY errors I found several regressions in v4l2-ioctl.c: 1) VIDIOC_ENUM/G/S/TRY_FMT would return -ENOTTY if the op for the particular format type was not set, even though the op for other types might have been present. In such a