On Saturday 22 May 2010 19:21:32 Ian Armstrong wrote:
On Saturday 22 May 2010, Andy Walls wrote:
On Sat, 2010-05-22 at 15:06 +0100, Andre Draszik wrote:
Hi,
As per the spec, the above ioctl codes are defined for inputs only -
it would be useful if there were similar codes for
Hi,
On Sun, May 23, 2010 at 12:20 PM, Hans Verkuil hverk...@xs4all.nl wrote:
On Saturday 22 May 2010 19:21:32 Ian Armstrong wrote:
On Saturday 22 May 2010, Andy Walls wrote:
On Sat, 2010-05-22 at 15:06 +0100, Andre Draszik wrote:
Some thoughts:
1. to me it appears that the ivtv driver
On Sunday 23 May 2010, Hans Verkuil wrote:
On Saturday 22 May 2010 19:21:32 Ian Armstrong wrote:
On Saturday 22 May 2010, Andy Walls wrote:
Some thoughts:
1. to me it appears that the ivtv driver looks like it ties the output
standard to the input standard currently (probably due
Hi,
As per the spec, the above ioctl codes are defined for inputs only -
it would be useful if there were similar codes for outputs.
I therefore propose to add the following:
VIDIOC_G_OUTPUT_STD
VIDIOC_S_OUTPUT_STD
VIDIOC_ENUM_OUTPUT_STD
which would behave similar to the above, but for output
On Sat, 2010-05-22 at 15:06 +0100, Andre Draszik wrote:
Hi,
As per the spec, the above ioctl codes are defined for inputs only -
it would be useful if there were similar codes for outputs.
I therefore propose to add the following:
VIDIOC_G_OUTPUT_STD
VIDIOC_S_OUTPUT_STD
On Saturday 22 May 2010, Andy Walls wrote:
On Sat, 2010-05-22 at 15:06 +0100, Andre Draszik wrote:
Hi,
As per the spec, the above ioctl codes are defined for inputs only -
it would be useful if there were similar codes for outputs.
I therefore propose to add the following:
