Re: msp3400 problem in linux-3.7.0

On Thu March 14 2013 00:08:57 Benjamin Schindler wrote: > Hi > > I recently upgraded from 3.2 to 3.7 and noticed, that I don't get any > sound anymore from my TV-card. tvtime still works fine, just with no > sound. As you can see from the snippet below, I have a hauppage WinTV > card which uses

[no subject]

bin7T9q2OarMG.bin Description: iso-8859-1

Re: [RFC 01/12] media: s5p-fimc: modify existing mdev to use common pipeline

Hi Shaik, On 03/11/2013 07:41 AM, Shaik Ameer Basha wrote: Hi Sylwester, Thanks for the review. Actually I know this is the important patch in this series and I wanted us to have enough time to discuss on this patch. That's why I posted this patch series in hurry. Sure, I'm glad it was posted

cron job: media_tree daily build: WARNINGS

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: Wed Mar 13 19:00:21 CET 2013 git branch: test git hash: 457ba4ce4f435d0b4dd82a0acc6c796e541a2ea7 gcc versio

Re: [PATCH] [media] dma-mapping: enable no mmu support in dma_common_mmap

Hello, On 3/6/2013 12:40 AM, Scott Jiang wrote: No MMU systems also make use of this function to do mmap. Signed-off-by: Scott Jiang --- drivers/base/dma-mapping.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/drivers/base/dma-mapping.c b/drivers/base/dma-mapping

[PATCH] drm/exynos: change the method for getting the interrupt resource of FIMD

Replaces the "platform_get_resource() for IORESOURCE_IRQ" with platform_get_resource_byname(). Both in exynos4 and exynos5, FIMD IP has 3 interrupts in the order: "fifo", "vsync", and "lcd_sys". But The FIMD driver expects the "vsync" interrupt to be mentioned as the 1st parameter in the FIMD DT no

Re: VIDIOC_ENUM_FMT bug query

dmesg: gspca_sn9c20x: OV7660 sensor detected regards Jonathan On 13/03/13 09:29, jonathan chetwynd wrote: Is there any further action I can take to discover whether a webcam can support a format? or to help develop a patch? the Sandberg Nightcam2 specification lists 1280 x 960 up to 15 frame

VIDIOC_ENUM_FMT bug query

Is there any further action I can take to discover whether a webcam can support a format? or to help develop a patch? the Sandberg Nightcam2 specification lists 1280 x 960 up to 15 frames per second but $ v4l2-ctl --list-formats-ext lists no such format as available regards Jonathan Chetwynd