Re: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]

On 26/07/13 18:37, Jakub Piotr Cłapa wrote: >> Using omapfb, or...? I hope not >> omap_vout, because that's rather unmaintained =). > > Laurent's live application is using the V4L2 API for video output (to > get free YUV conversion and DMA) so I guess this unfortunatelly counts > as using omap_vo

Re: [REVIEW PATCH 4/6] exynos4-is: Add clock provider for the external clocks

Hi Sylwester, On Wed, Jul 24, 2013 at 12:09 AM, Sylwester Nawrocki wrote: > This patch adds clock provider to expose the sclk_cam0/1 clocks > for image sensor subdevs. > > Signed-off-by: Sylwester Nawrocki > Signed-off-by: Kyungmin Park > --- > .../devicetree/bindings/media/samsung-fimc.txt

Re: [REVIEW PATCH 0/6] exynos4-is: Asynchronous subdev registration support

Hi Sylwester, On Wed, Jul 24, 2013 at 12:09 AM, Sylwester Nawrocki wrote: > This patch series is a refactoring of the exynos4-is driver to get rid > of the common fimc-is-sensor driver and to adapt it to use "standard" > sensor subdev drivers, one per each image sensor type. > Then a clock provid

[PATCH 0/3] networking: Use ETH_ALEN where appropriate

Convert the uses mac addresses to ETH_ALEN so it's easier to find and verify where mac addresses need to be __aligned(2) Joe Perches (3): uapi: Convert some uses of 6 to ETH_ALEN include: Convert ethernet mac address declarations to use ETH_ALEN ethernet: Convert mac address uses of 6 to ETH

[PATCH 2/3] include: Convert ethernet mac address declarations to use ETH_ALEN

It's convenient to have ethernet mac addresses use ETH_ALEN to be able to grep for them a bit easier and also to ensure that the addresses are __aligned(2). Add #include as necessary. Signed-off-by: Joe Perches --- include/acpi/actbl2.h | 4 ++- include/linux/dm9000.h | 4

Green/purple video from 950Q + security cam

Hi, I have a WinTV-HVR-950Q which I am using to capture composite video. I have two cameras: a rear-view cam for a car, and a security camera. When I plug either of these cameras into the video plug on a plain old TV, they work great. When I plug either camera into the 950Q on Windows usin

[PATCH 2/2] tea575x: Move from sound to media

Move tea575x from sound/i2c/other to drivers/media/radio Includes Kconfig changes by Hans Verkuil. Signed-off-by: Hans Verkuil Signed-off-by: Ondrej Zary --- drivers/media/radio/Kconfig | 12 +- drivers/media/radio/Makefile|1 + drivers/media/radio/tea575x.c | 584 +

[PATCH 1/2] tea575x: Move header from sound to media

Move include/sound/tea575x-tuner.h to include/media/tea575x.h and update files that include it. Signed-off-by: Ondrej Zary --- drivers/media/radio/radio-maxiradio.c |2 +- drivers/media/radio/radio-sf16fmr2.c |2 +- drivers/media/radio/radio-shark.c |2 +- include/media/tea575x

[PATCH 0/2] tea575x: Move from sound to media

Hello, TEA575x is neither a sound device nor an i2c device. Let's finally move it from sound/i2c/other to drivers/media/radio. Tested with snd-es1968, snd-fm801 and radio-sf16fmr2. -- Ondrej Zary -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message

Re: PROBLEM: dvb-usb-rtl28xxu and Terratec Cinergy TStickRC (rev3) - no signal on some frequencies

Hello Antti, Unfortunately the patch doesn't work for me either. Would it help you if I send you an usb sniff with wireshark of an program search run with kaffeine (27 MB)? regards Torsten Am 24.07.2013 16:06, schrieb Antti Palosaari: Could you test attached patch? It enhances reception a

cron job: media_tree daily build: ERRORS

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 Jul 28 19:00:16 CEST 2013 git branch: test git hash: 51dd4d70fc59564454a4dcb90d6d46d39a4a97ef gcc versi

Re: Very verbose message about em28174 chip.

Am 28.07.2013 16:05, schrieb Devin Heitmueller: > On Sun, Jul 28, 2013 at 9:58 AM, Chris Rankin wrote: >> - Original Message - >> >> From: Devin Heitmueller >> >>> The amount of output is not inconsistent with most other linuxtv drivers >>> though. >> It's the EEPROM dump that really cau

Re: Very verbose message about em28174 chip.

On Sun, Jul 28, 2013 at 9:58 AM, Chris Rankin wrote: > - Original Message - > > From: Devin Heitmueller > >>The amount of output is not inconsistent with most other linuxtv drivers >>though. > > It's the EEPROM dump that really caught my eye: 16+ lines of pure "WTF?". Yeah, nowadays the

Re: Very verbose message about em28174 chip.

- Original Message - From: Devin Heitmueller >The amount of output is not inconsistent with most other linuxtv drivers >though. It's the EEPROM dump that really caught my eye: 16+ lines of pure "WTF?". Cheers, Chris -- To unsubscribe from this list: send the line "unsubscribe linux-me

Re: Very verbose message about em28174 chip.

On Sun, Jul 28, 2013 at 9:19 AM, Chris Rankin wrote: > Hi, > > I plugged my PCTV 290e device into my newly compiled 3.10.3 kernel today, and > found this message in the dmesg log. > > > [ 511.041412] usb 10-4: new high-speed USB device number 3 using ehci-pci > [ 511.216218] em28xx: New device

Re: Very verbose message about em28174 chip.

Hi, It's normal for em28xx to give you that sort of information on device-plug - it does seem like a lot, but it's effectively "one-off" and you probably won't see much else during use of the device, under default module parameters. It's very useful log output if you have a new device or a sl

Very verbose message about em28174 chip.

Hi, I plugged my PCTV 290e device into my newly compiled 3.10.3 kernel today, and found this message in the dmesg log. [  511.041412] usb 10-4: new high-speed USB device number 3 using ehci-pci [  511.216218] em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0

Re: de-Primacom initial tuning data doesn't work anymore

I completly missed that mail somehow, appologies, a CC to me is always helpfull ;) Next time it would be preferred if you send a patch instead of a link. It would have been even better if Sven submittted said patch so we could have committed it to git much earlier! Anyhow, pushed to git(hub)