[linux-dvb] Re: 2.6.10-rc2 + dvb-kernel problem

[Andrew de Quincey <adq_dvb@lidskialf.net>]

On Thursday 18 Nov 2004 18:31, Johannes Stezenbach wrote:
> Joerg Riechardt wrote:
> > right, my frontend is mt312 and I only loaded that. When I load also
> > mt352 and stv0299 (that are the ones dmesg complains about), insmod load
> > works, but now I get
> >
> > vdr kernel: master_xfer: write error 0 !
> > vdr kernel: message 0: flags=0x0, addr=0x68, buf[0]=0x2, len=2
> > vdr kernel: master_xfer: read error !
> > vdr kernel: message 0: flags=0x0, addr=0x68, buf=0x0, len=1
> > vdr kernel: message 1: flags=0x1, addr=0x68, buf=0x0, len=1
> > vdr kernel: master_xfer: read error !
> > vdr kernel: message 0: flags=0x0, addr=0xf, buf=0x7f, len=1
> > vdr kernel: message 1: flags=0x1, addr=0xf, buf=0x0, len=1
> > vdr kernel: mt352_read_register: readreg error (ret == -121)
> > vdr kernel: skystar2: A frontend driver was not found for device
> > 13d0/2103 subsystem 13d0/2103
> >
> > what can I do?
>
> Looks like mt312 support got lost during FE_REFACTORING.
> skystar2.c:master_xfer() is also too verbose, as some
> i2c transfers are bound to fail during frontend probing.
>
> If you want to hack it yourself, start with frontend_init()
> in skystar2.c, and compare to the skystar2.c tagged with
> OLD_11_HEAD_2004_10_28.
>
> Or wait until Andrew or someone else does it.

Aha, I'll get on it. So the demod is an mt312. Can you tell me what is printed 
on the tin box on your card please? Shouldn't take me long once I know that 
info...