cron job: media_tree daily build: OK

2015-07-02 Thread Hans Verkuil
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Fri Jul 3 04:00:19 CEST 2015 git branch: test git hash: 5bab86243d949cf021b0f104faafc18f5d20283c gcc versi

Re: dvb_usb_af9015: command failed=1 _ kernel >= 4.1.x

2015-07-02 Thread poma
On 26.05.2015 14:24, poma wrote: > > If it is not taken into account the already known problem of unreliable > operation of the first tuner of the two, > the device works reliably within kernel 4.0.4 with mxl5007t.ko reverted to > http://git.linuxtv.org/cgit.cgi/media_tree.git/commit/drivers/medi

Subjective maturity of tw6869, cx25821, bluecherry/softlogic drivers

2015-07-02 Thread Nathaniel Bezanson
Hi all, If this isn't the appropriate venue for this question, please gently steer me somewhere else. Thanks. :) I'm trying to head off the "well you shouldn't have bought *that* junk in the first place!" advice by doing some research ahead of time, and I'm here to check some assumptions. I've

[PATCH] DocBook: fix media-ioc-device-info.xml type

2015-07-02 Thread Hans Verkuil
The documentation had two media_version entries. The second one was a typo and it should be driver_version instead. Correct this. Signed-off-by: Hans Verkuil diff --git a/Documentation/DocBook/media/v4l/media-ioc-device-info.xml b/Documentation/DocBook/media/v4l/media-ioc-device-info.xml index

[RFCv3 PATCH 2/2] DocBook/media: document VIDIOC_SUBDEV_QUERYCAP

2015-07-02 Thread Hans Verkuil
From: Hans Verkuil Add documentation for the new VIDIOC_SUBDEV_QUERYCAP ioctl. Signed-off-by: Hans Verkuil --- Documentation/DocBook/media/v4l/v4l2.xml | 1 + .../DocBook/media/v4l/vidioc-subdev-querycap.xml | 133 + 2 files changed, 134 insertions(+) create

[RFCv3 PATCH 1/2] v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl

2015-07-02 Thread Hans Verkuil
From: Hans Verkuil While normal video/radio/vbi/swradio nodes have a proper QUERYCAP ioctl that apps can call to determine that it is indeed a V4L2 device, there is currently no equivalent for v4l-subdev nodes. Adding this ioctl will solve that, and it will allow utilities like v4l2-compliance to

[RFCv3 PATCH 0/2] Add VIDIOC_SUBDEV_QUERYCAP

2015-07-02 Thread Hans Verkuil
From: Hans Verkuil This patch series adds the VIDIOC_SUBDEV_QUERYCAP ioctl for v4l-subdev devices as discussed during the ELC in San Jose and as discussed here: http://www.spinics.net/lists/linux-media/msg88009.html This patch series returns to the v1 patch series, but it drops the pads field a

Re: [RFC PATCH 1/3] v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl

2015-07-02 Thread Hans Verkuil
Hi Sakari, On 07/02/15 15:01, Sakari Ailus wrote: > Hi Hans, > > Thanks for the patch! > > On Fri, May 01, 2015 at 01:33:48PM +0200, Hans Verkuil wrote: >> From: Hans Verkuil >> >> While normal video/radio/vbi/swradio nodes have a proper QUERYCAP ioctl >> that apps can call to determine that it

Re: [RFC PATCH 1/3] v4l2-subdev: add VIDIOC_SUBDEV_QUERYCAP ioctl

2015-07-02 Thread Sakari Ailus
Hi Hans, Thanks for the patch! On Fri, May 01, 2015 at 01:33:48PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > While normal video/radio/vbi/swradio nodes have a proper QUERYCAP ioctl > that apps can call to determine that it is indeed a V4L2 device, there > is currently no equivalent for

Re: [RFCv2 PATCH 0/8] Add VIDIOC_SUBDEV_QUERYCAP and use MEDIA_IOC_DEVICE_INFO

2015-07-02 Thread Laurent Pinchart
Hi Hans, Thank you for the patches. On Wednesday 06 May 2015 08:57:15 Hans Verkuil wrote: > From: Hans Verkuil > > This patch series adds the VIDIOC_SUBDEV_QUERYCAP ioctl for v4l-subdev > devices as discussed during the ELC in San Jose and as discussed here: > > http://www.spinics.net/lists/li

[RFC] How to get current position/status of iris/focus/pan/tilt/zoom?

2015-07-02 Thread Hans Verkuil
When using V4L2_CID_IRIS/FOCUS/PAN/TILT/ZOOM_ABSOLUTE/RELATIVE, how do you know when the new position has been reached? If this is controlled through a motor, then it may take some time and ideally you would like to be able to get the current absolute position (if the hardware knows) and whether th