-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 18.03.2011 01:08, schrieb Dmitri Belimov:
> Hi
>
> Add compatibility for composite and s-video inputs. Some TV cards
hasn't it.
> Fix S-Video input, the s-video cable has only video signals no audio.
Call the function of audio configure kill chrom
On 03/18/2011 11:27 PM, Florian Mickler wrote:
On Fri, 18 Mar 2011 18:34:58 +0200
Antti Palosaari wrote:
On 03/15/2011 10:43 AM, Florian Mickler wrote:
usb_control_msg initiates (and waits for completion of) a dma transfer using
the supplied buffer. That buffer thus has to be seperately alloc
On Fri, 18 Mar 2011 18:36:53 +0200
Antti Palosaari wrote:
> On 03/15/2011 10:43 AM, Florian Mickler wrote:
> > usb_control_msg initiates (and waits for completion of) a dma transfer using
> > the supplied buffer. That buffer thus has to be seperately allocated on
> > the heap.
> >
> > In lib/dma_
On Fri, 18 Mar 2011 18:36:11 +0200
Antti Palosaari wrote:
> On 03/15/2011 10:43 AM, Florian Mickler wrote:
> > usb_control_msg initiates (and waits for completion of) a dma transfer using
> > the supplied buffer. That buffer thus has to be seperately allocated on
> > the heap.
> >
> > In lib/dma_
On Fri, 18 Mar 2011 18:34:58 +0200
Antti Palosaari wrote:
> On 03/15/2011 10:43 AM, Florian Mickler wrote:
> > usb_control_msg initiates (and waits for completion of) a dma transfer using
> > the supplied buffer. That buffer thus has to be seperately allocated on
> > the heap.
> >
> > In lib/dma_
Issa Gorissen wrote:
On 13/03/11 11:47, Martin Vidovic wrote:
Btw, we should choose a more meaningful name for 'camX'.
I would prefer something like cainoutX or caioX or cinoutX or cioX.
I agree, camX could be misleading since it's not necessarily a CAM
application.
According to E
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Fri Mar 18 19:00:34 CET 2011
git hash:41f3becb7bef489f9e8c35284dd88a1ff59b190c
gcc version: i686-linux-gcc (GCC) 4.5.
On Thu, 2011-03-17 at 08:46 -0300, Mauro Carvalho Chehab wrote:
> On a quick test, it seems that it doesn't recognize the tcpdump file
> format (at least, it was not able to capture the dump files I got
> with the beagleboard). Adding support for it could be an interesting
> addition to your cod
Can anyone identify which are used chips for USB DVB-T + analog card
"AMD Cali TV card" sold vary many brands?
http://crunchbanglinux.org/forums/topic/5642/usb-tv-tuner-help/
I have one of those, but I don't want break case...
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: se
On 03/15/2011 10:43 AM, Florian Mickler wrote:
usb_control_msg initiates (and waits for completion of) a dma transfer using
the supplied buffer. That buffer thus has to be seperately allocated on
the heap.
In lib/dma_debug.c the function check_for_stack even warns about it:
WARNING: at l
On 03/15/2011 10:43 AM, Florian Mickler wrote:
usb_control_msg initiates (and waits for completion of) a dma transfer using
the supplied buffer. That buffer thus has to be seperately allocated on
the heap.
In lib/dma_debug.c the function check_for_stack even warns about it:
WARNING: at l
On 03/15/2011 10:43 AM, Florian Mickler wrote:
usb_control_msg initiates (and waits for completion of) a dma transfer using
the supplied buffer. That buffer thus has to be seperately allocated on
the heap.
In lib/dma_debug.c the function check_for_stack even warns about it:
WARNING: at l
What happened to this driver in linux-next of 2011.0318?
It's in linux-next of 2011.0317.
Here's a patch that was prepared against linux-next of 2011.0317.
---
From: Randy Dunlap
Fix text spacing and grammar.
Fix printk format warning:
drivers/media/radio/wl128x/fmdrv_common.c:274: warning: fo
On 03/08/2011 12:12 AM, adq wrote:
Ah well, so its definitely /not/ conflicting i2c writes that cause the
tuner problem as it has finally just died. The festats for a "crashed"
tuner are:
Sig: 50933 SNR: 50 BER: 0 UBLK: 5370554 Stat: 0x01 [SIG ]
(no other error messages)
For the other tun
Hi Hermann,
> Hopefully it does help in that other case.
I have it working now. I had to add a delay of 120 seconds in the
mythtv backend script to allow the driver enough time to scan both
cards and install the firmware properly. Previously the mythtv
backend at startup was trying to talk to t
15 matches
Mail list logo