Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: Kernel Oops with saa7134 (v4l / analogue) + dvb-ttusb-budget



On Monday 04 Oct 2004 13:03, Richard Taylor wrote:
> Hi all,
>
> I have been trying to get my WinTV Nova-T USB Digital receiver to work
> alongside an saa7134 fly-view / video based analogue receiver.
>
> Insmodding, and using these drivers independantly is no problem, however
> when inserting them together causes my kernel to get upset.
>
> I am using the current (04/Sept/2004) CVS for dvb-kernel, and have tried
> both the kernel saa7134, and the latest v4l release (saa7134-0.2.12).
>
> Two Kernels tried:
> linux-2.6.7-gentoo-r9
> linux-2.6.9-rc2
>
> The 2.6.7 took some mods to get the dvb-kernel to compile (kvect?)
>
>
> That's another story :)
>
> As stated above, on their own, both drivers work, together they fail.
> The result is similar for both 2.6.7 and 2.6.9
>
> ---- begin dmseg output ----
>
> saa7130/34: v4l2 driver version 0.2.11 loaded
> saa7134[0]: found at 0000:00:0e.0, rev: 1, irq: 17, latency: 32, mmio:
> 0xe4000000 saa7134[0]: subsystem: 1043:0210, board: KNC One TV-Station RDS
> / Typhoon TV Tuner RDS [card=7,insmod option] saa7134[0]: board init: gpio
> is 10700
> tuner: chip found at addr 0xc0 i2c-bus saa7134[0]
> tuner: type set to 10 (Alps TSBE1) by saa7134[0]
> tda9887: chip found @ 0x86

It looks like the tda9887 device is erroneously clamining the same i2c device 
as the ALPS TDMB7 device. I've seen this as well with the cx88 DVB-T cards. 
If you can avoid loading one of those modules, that would be the easiest way 
to fix it.

Otherwise.. umm, you'll either have to hack something in yourself to stop the 
tda9887 from jumping on the bus, or wait for the new code refactoring + 
kernel i2c fixes.




Home | Main Index | Thread Index