On 2012-09-16 00:25, Mauro Carvalho Chehab wrote:
Em Sat, 15 Sep 2012 20:12:49 +0200
Anders Thomsonaerikss...@gmail.com escreveu:
On 2012-09-15 19:58, Mauro Carvalho Chehab wrote:
Em Sat, 15 Sep 2012 19:39:31 +0200
Anders Thomsonaerikss...@gmail.com escreveu:
On
Hi,
Am 13.09.2012 14:05, schrieb Hans de Goede:
Hi,
On 09/12/2012 04:36 PM, Frank Schäfer wrote:
snip
And a negative side effect is, that unknown pac7302 devices (with no
V4LCONTROL_ROTATED_90_JPEG entry in libv4lconvert) do not work.
With a consistent API behavior, they would work fine
On Sat September 15 2012 22:16:24 Sylwester Nawrocki wrote:
On 09/15/2012 02:35 PM, Hans Verkuil wrote:
If we switch all existing drivers to monotonic timestamps in kernel
release
3.x, v4l2-compliance can just use the version it gets from
VIDIOC_QUERYCAP and
enforce monotonic
On 09/12/2012 09:32 AM, Marx wrote:
Hello
I'm trying to use dual DVB-T tuner based on ITE9135 tuner. I use Debian
kernel 3.5-trunk-686-pae. My motherboard is AsRock E350M1 (no USB3 ports).
Tuner is detected ok, see log at the end of post.
When I try to scan channels, bug happens:
Sep 11
On Sunday 16 September 2012 15:57:14 Hans Verkuil wrote:
On Sat September 15 2012 22:16:24 Sylwester Nawrocki wrote:
On 09/15/2012 02:35 PM, Hans Verkuil wrote:
If we switch all existing drivers to monotonic timestamps in kernel
release
3.x, v4l2-compliance can just use the version it
Guys I'm adding v4l2 output device support for VLC/ffmpeg/libav (I'm using
v4l2loopback [1] driver for testing) but I have a problem which I can't seem
to find a solution.
VLC [2] uses VIDIOC_CROPCAP [3] to detect the pixelaspect ratio of the input
it receives from v4l2 device. But I can't seem
Currently used registers 0xc5 and 0xc7 provide only a very coarse
adjustment possibility within a very small value range (0-3).
With registers 0x01 and 0x03, a fine grained adjustment with
255 steps is possible. This is also what the Windows driver does.
Signed-off-by: Frank Schäfer
We already support the red balance (V4L2_CID_RED_BALANCE) and
blue balance (V4L2_CID_BLUE_BALANCE) controls and lots of hardware
provides a possibility to adjust the green balance, too.
Several drivers already support this as custom controls, other just
don't do that due to the lack of a V4L2
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/gspca/pac7302.c | 23 ++-
1 files changed, 22 insertions(+), 1 deletions(-)
diff --git a/drivers/media/usb/gspca/pac7302.c
b/drivers/media/usb/gspca/pac7302.c
index 8a0f4d6..9b62b74 100644
---
Any pointers where else to look? I'm kinda lost at the moment :)
Oliver
On 09/10/12 19:28, Oliver Schinagl wrote:
On 09/10/12 16:29, Oliver Schinagl wrote:
On 10-09-12 13:46, Antti Palosaari wrote:
On 09/10/2012 12:58 PM, Oliver Schinagl wrote:
Changed the address as recommended, which
On Sun September 16 2012 17:32:52 Georgi Chorbadzhiyski wrote:
Guys I'm adding v4l2 output device support for VLC/ffmpeg/libav (I'm using
v4l2loopback [1] driver for testing) but I have a problem which I can't seem
to find a solution.
VLC [2] uses VIDIOC_CROPCAP [3] to detect the pixelaspect
Hello
You have about all the possible info. There is chipset vendor driver
look example and existing Linux drivers for all the used chips. Just few
lines of code needed for the device profile. I surely can help, but it
is not something I would like to teach and say do that and test that. It
On 9/16/12 7:28 PM, Hans Verkuil wrote:
On Sun September 16 2012 17:32:52 Georgi Chorbadzhiyski wrote:
Guys I'm adding v4l2 output device support for VLC/ffmpeg/libav (I'm using
v4l2loopback [1] driver for testing) but I have a problem which I can't seem
to find a solution.
VLC [2] uses
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
Since all the pieces should be there, fc2580 driver, af9033/5 driver,
it's just a matter of glueing things together, right? I'll dig
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
You could capture data from Linux too (eg. Wireshark).
But with a little experience you
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:Sun Sep 16 19:00:20 CEST 2012
git hash:36aee5ff9098a871bda38dbbdad40ad59f6535cf
gcc version: i686-linux-gcc
On Fri, Sep 14, 2012 at 10:58:53AM +0300, Timo Kokkonen wrote:
It appears that all modern lirc drivers are now using the rc-core
functionalities to implement the common stuff. When the rx51 lirc driver
was first written, the core was not in place yet. Therefore it is
implementing the file
On 09/16/2012 05:33 PM, Laurent Pinchart wrote:
On Sunday 16 September 2012 15:57:14 Hans Verkuil wrote:
On Sat September 15 2012 22:16:24 Sylwester Nawrocki wrote:
On 09/15/2012 02:35 PM, Hans Verkuil wrote:
If we switch all existing drivers to monotonic timestamps in kernel
release
3.x,
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
You could capture data from Linux too (eg.
On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
Hi Mauro,
On 2012년 09월 16일 00:38, Mauro Carvalho Chehab wrote:
-EMISSINGMAKEFILE
Without a Makefile, the driver will not compile, causing
breakages for arm exynos5 sub-architecture.
Cc: Shaik Ameer Basha shaik.am...@samsung.com
Cc: Sungchun Kang sungchun.k...@samsung.com
Cc: Seung-Woo
Disable RXEN and enable RESETN pins on attach to ensure chip is
totally powered down after attach.
Signed-off-by: Antti Palosaari cr...@iki.fi
---
drivers/media/tuners/tua9001.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/media/tuners/tua9001.c
Signed-off-by: Antti Palosaari cr...@iki.fi
---
drivers/media/usb/dvb-usb-v2/af9035.c | 65 ++-
1 file changed, 48 insertions(+), 17 deletions(-)
diff --git a/drivers/media/usb/dvb-usb-v2/af9035.c
b/drivers/media/usb/dvb-usb-v2/af9035.c
index 89cc901..84b3b27
This reduces power consumption 10mA.
Signed-off-by: Antti Palosaari cr...@iki.fi
---
drivers/media/dvb-frontends/af9033.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/media/dvb-frontends/af9033.c
b/drivers/media/dvb-frontends/af9033.c
index 0979ada..56e9611 100644
---
The series enables multi-platform support for imx. Since the required
frameworks (clk, pwm) and spare_irq have already been adopted on imx,
the series is all about cleaning up mach/* headers. Along with the
changes, arch/arm/plat-mxc gets merged into arch/arm/mach-imx.
It's based on a bunch of
The mx1_camera driver has been broken for a few release cycles since
commit 6bd0812 (dmaengine: imx-dma: merge old dma-v1.c with imx-dma.c).
It seems there is no one even compile tested it since then, as doing
so will end up with the following error.
CC drivers/media/video/mx1_camera.o
In
The header ipu.h really belongs to dma subsystem rather than imx
platform. Rename it to ipu-dma.h and put it into include/linux/dma/.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Vinod Koul vinod.k...@intel.com
Cc: Guennadi Liakhovetski g.liakhovet...@gmx.de
Cc: Florian Tobias Schandinat
This is a piece of code becoming dead since commit 2c9ba37 ([media]
V4L: mx2_camera: remove unsupported i.MX27 DMA mode, make EMMA
mandatory). It should have been removed together with the commit.
Remove it now.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Guennadi Liakhovetski
Use managed functions to clean up the error handling code and function
mx2_camera_remove(). Along with the change, a few variables get removed
from struct mx2_camera_dev.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Guennadi Liakhovetski g.liakhovet...@gmx.de
Cc: linux-media@vger.kernel.org
It changes the driver to use platform_device_id rather than cpu_is_xxx
to determine the controller type, and updates the platform code
accordingly.
As the result, mach/hardware.h inclusion gets removed from the driver.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Guennadi Liakhovetski
30 matches
Mail list logo
