Hi,
i have problems dtv-scan-tables dvbv5 part.
1. better a new subdirectory to equalant to dvb (i.e. dvbv5)
2. the block names must add a index number (format BerlinX - X is a
number, i.e. first block: Berlin1, second block: Berlin2 etc. not first
block: Berlin, second block: Berlin),
Hello,
On 2014-08-08 14:59, Hans Verkuil wrote:
Modern kernels enable dynamic printk support, which is fine, except when it is
combined with a debug module option. Enabling debug in videobuf2-core now
produces
no debugging unless it is also enabled through the dynamic printk support in
This is used by the I2C code in order to slow down the
speed to 20 kHz on devices with xc5000 or xc5000c.
So, we need it to be filled for all devices.
Signed-off-by: Mauro Carvalho Chehab m.che...@samsung.com
---
drivers/media/usb/au0828/au0828-cards.c | 12 ++--
1 file changed, 6
Right now, the au0828 driver uses .tuner to detect if analog
tv is being used or not. By not filling .tuner fields at the
board struct, the I2C core can't do decisions based on it.
So, add a field to explicitly tell when analog TV is supported.
No functional changes.
Signed-off-by: Mauro
We need to have the tuner type filed for all devices, for the
logic inside the I2C core to work. So, warrant that tuner type
can be used by all entries and add the proper values there.
Mauro Carvalho Chehab (2):
au0828: explicitly identify boards with analog TV
au0828: fill tuner type on all
On 08/18/2014 11:51 AM, Mauro Carvalho Chehab wrote:
Right now, the au0828 driver uses .tuner to detect if analog
tv is being used or not. By not filling .tuner fields at the
board struct, the I2C core can't do decisions based on it.
So, add a field to explicitly tell when analog TV is
Em Mon, 18 Aug 2014 12:33:39 +
Hans Verkuil hverk...@xs4all.nl escreveu:
On 08/18/2014 11:51 AM, Mauro Carvalho Chehab wrote:
Right now, the au0828 driver uses .tuner to detect if analog
tv is being used or not. By not filling .tuner fields at the
board struct, the I2C core can't do
Hi Mr. Chen,
Em Mon, 18 Aug 2014 13:36:11 +0800
Bimow Chen bimow.c...@ite.com.tw escreveu:
From 7f12471b97ff0a81a97d9133e10a5ebe4e7c0c11 Mon Sep 17 00:00:00 2001
From: Bimow Chen bimow.c...@ite.com.tw
Date: Fri, 15 Aug 2014 13:44:19 +0800
Subject: [PATCH] it9135: add firmware v3.25.0.0 for
Simplify ioctl handling by using video_ioctl2.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
drivers/usb/gadget/function/f_uvc.c| 1 +
drivers/usb/gadget/function/uvc_v4l2.c | 298 +
2 files changed, 158 insertions(+), 141
To handle class requests received on ep0, the driver needs to access the
length and direction of the request after the setup stage. It currently
stores them in a v4l2 event during the setup stage, and then copies them
from the event structure to the driver internal state structure when the
event
Hello,
This small patch series replaces manual handling of V4L2 ioctls in the UVC
gadget function driver with the video_ioctl2 infrastructure. This simplifies
the driver and brings support for V4L2 tracing features.
The series is based on top of Michael Grzeschik's usb: gadget/uvc: remove
On 08/18/2014 05:06 PM, Laurent Pinchart wrote:
Simplify ioctl handling by using video_ioctl2.
Are you able to test this on actual hardware? And if so, can you run
v4l2-compliance?
Regards,
Hans
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
On Thu, 2014-08-14 at 07:39 +0300, Sakari Ailus wrote:
Bryan and Richard,
Your opinion would be much appreciated to a question myself and Jacek were
pondering. Please see below.
On Thu, Aug 07, 2014 at 03:12:09PM +0200, Jacek Anaszewski wrote:
Hi Sakari,
On 08/04/2014 02:50 PM,
Hi Richard,
Richard Purdie wrote:
On Thu, 2014-08-14 at 07:39 +0300, Sakari Ailus wrote:
Bryan and Richard,
Your opinion would be much appreciated to a question myself and Jacek were
pondering. Please see below.
On Thu, Aug 07, 2014 at 03:12:09PM +0200, Jacek Anaszewski wrote:
Hi Sakari,
Hi Hans,
On Monday 18 August 2014 18:24:26 Hans Verkuil wrote:
On 08/18/2014 05:06 PM, Laurent Pinchart wrote:
Simplify ioctl handling by using video_ioctl2.
Are you able to test this on actual hardware? And if so, can you run
v4l2-compliance?
I'm afraid not. I don't have a platform with
Hi Ian,
Thank you for the patch.
On Monday 11 August 2014 13:05:18 Ian Molton wrote:
This patch adds necessary support for the ADV7612 dual HDMI decoder /
repeater chip.
This was tested using a heavily modified rcar_vin/soc_camera capture driver.
Tested-by: William Towle
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: Tue Aug 19 04:00:14 CEST 2014
git branch: test
git hash: 0f3bf3dc1ca394a8385079a5653088672b65c5c4
gcc
17 matches
Mail list logo
