[linux-dvb] Dposh DVB-T USB2.0 seems to not work properly

Andrew Websdale websdaleandrew at googlemail.com
Tue Jun 24 21:09:26 CEST 2008


2008/6/24 Antti Palosaari <crope at iki.fi>:

> ma 23.6.2008 21:58 Andrew Websdale kirjoitti:
>
> >> I've tried adding the mt2060 code - it compiles OK & does seem to be
> >> nearly
> >> right,the tuner is being recognised, but I think loading the module
> >> causes
> >> the I2c bit of the kernel to Oops - would an incorrect i2c address cause
> >> this?
> >>
> > Here's my dmesg output:
> > m920x_mt2060_tuner_attach
> > BUG: unable to handle kernel NULL pointer dereference at virtual address
> > 0000006c
>
> because you have passed tuner i2c-address as parameter to the dvb_attach()




I've changed the parameter to '&adap->dev->i2c_adap' & I now get this dmesg
output:

dvb-usb: found a 'Dposh(mt2060 tuner) DVB-T USB2.0' in cold state, will try
to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dposh-01.fw'
80 0 b0 0
ff
firmware uploaded!
dvb_usb_m920x: probe of 5-1:1.0 failed with error 64
usb 5-1: USB disconnect, address 4
usb 5-1: new high speed USB device using ehci_hcd and address 5
usb 5-1: configuration #1 chosen from 1 choice
Probing for m920x device at interface 0
dvb-usb: found a 'Dposh(mt2060 tuner) DVB-T USB2.0' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
DVB: registering new adapter (Dposh(mt2060 tuner) DVB-T USB2.0)
m920x_mt352_frontend_attach
DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
m920x_mt2060_tuner_attach
MT2060: successfully identified (IF1 = 1220)
dvb-usb: Dposh(mt2060 tuner) DVB-T USB2.0 successfully initialized and
connected.

so far so good :) , but when I scan with Kaffeine I get this:

Demod init!    //this repeated ~ 30 times

mt352_read_register: readreg error (reg=3, ret==-110)  //then this block or
mt2060 I2C write failed (len=2)                           //similar repeated
until end of scan
mt2060 I2C write failed (len=6)
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt2060 I2C read failed
mt352_write() to reg 51 failed (err = -110)!
mt352_write() to reg 5e failed (err = -110)!


Could this just be due to not getting the .i2c_address set in the
'm920x_mt2060_config' struct correct, or is it another dumb error on my
part?
cheers for the help,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20080624/511e65ad/attachment.htm 


More information about the linux-dvb mailing list