On Monday 05 April 2010 04:58:02 Andy Walls wrote:
On Sun, 2010-04-04 at 17:41 +0200, Hans Verkuil wrote:
Hi all,
The support in drivers for the V4L2 control API is currently very chaotic.
Few if any drivers support the API correctly. Especially the support for the
new extended
Hans Verkuil wrote:
On Monday 05 April 2010 04:58:02 Andy Walls wrote:
On Sun, 2010-04-04 at 17:41 +0200, Hans Verkuil wrote:
Hi all,
The support in drivers for the V4L2 control API is currently very chaotic.
Few if any drivers support the API correctly. Especially the support for the
new
On Sun, Apr 4, 2010 at 10:58 PM, Andy Walls awa...@md.metrocast.net wrote:
I think I have 2 cases where that is undesriable:
1. cx18 volume control: av_core subdev has a volume control (which the
bridge driver currently reports as it's volume control) and the cs5435
subdev has a volume
On Monday 05 April 2010 17:41:47 Mauro Carvalho Chehab wrote:
Hans Verkuil wrote:
On Monday 05 April 2010 04:58:02 Andy Walls wrote:
On Sun, 2010-04-04 at 17:41 +0200, Hans Verkuil wrote:
Hi all,
The support in drivers for the V4L2 control API is currently very chaotic.
Few if any
On Monday 05 April 2010 20:11:13 Hans Verkuil wrote:
Another option would be to set aside a range of IDs at the end of each control
class that could be used as a 'remap' area.
For example: the IDs for user class controls go from 0x98-0x98. Of
which anything = 0x981000 is a private
Hi Hans,
On Sunday 04 April 2010 17:41:51 Hans Verkuil wrote:
Hi all,
The support in drivers for the V4L2 control API is currently very chaotic.
Few if any drivers support the API correctly. Especially the support for
the new extended controls is very much hit and miss.
Combine that with
On Mon, 2010-04-05 at 11:25 +0200, Hans Verkuil wrote:
On Monday 05 April 2010 04:58:02 Andy Walls wrote:
On Sun, 2010-04-04 at 17:41 +0200, Hans Verkuil wrote:
1. cx18 volume control: av_core subdev has a volume control (which the
bridge driver currently reports as it's volume control)
Hi all,
The support in drivers for the V4L2 control API is currently very chaotic.
Few if any drivers support the API correctly. Especially the support for the
new extended controls is very much hit and miss.
Combine that with the requirements for the upcoming embedded devices that
will want to
On Sun, 2010-04-04 at 17:41 +0200, Hans Verkuil wrote:
Hi all,
The support in drivers for the V4L2 control API is currently very chaotic.
Few if any drivers support the API correctly. Especially the support for the
new extended controls is very much hit and miss.
Combine that with the
