<br><br><div class="gmail_quote">2008/6/24 Antti Palosaari <<a href="mailto:crope@iki.fi">crope@iki.fi</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
ma 23.6.2008 21:58 Andrew Websdale kirjoitti:<br>
<div class="Ih2E3d"><br>
>> I've tried adding the mt2060 code - it compiles OK & does seem to be<br>
>> nearly<br>
>> right,the tuner is being recognised, but I think loading the module<br>
>> causes<br>
>> the I2c bit of the kernel to Oops - would an incorrect i2c address cause<br>
>> this?<br>
>><br>
> Here's my dmesg output:<br>
</div><div class="Ih2E3d">> m920x_mt2060_tuner_attach<br>
> BUG: unable to handle kernel NULL pointer dereference at virtual address<br>
> 0000006c<br>
<br>
</div>because you have passed tuner i2c-address as parameter to the dvb_attach()</blockquote><div><br><br><br>I've changed the parameter to '&adap->dev->i2c_adap' & I now get this dmesg output:<br>
<br>dvb-usb: found a 'Dposh(mt2060 tuner) DVB-T USB2.0' in cold state, will try to load a firmware<br>dvb-usb: downloading firmware from file 'dvb-usb-dposh-01.fw'<br>80 0 b0 0<br>ff<br>firmware uploaded!<br>
dvb_usb_m920x: probe of 5-1:1.0 failed with error 64<br>usb 5-1: USB disconnect, address 4<br>usb 5-1: new high speed USB device using ehci_hcd and address 5<br>usb 5-1: configuration #1 chosen from 1 choice<br>Probing for m920x device at interface 0<br>
dvb-usb: found a 'Dposh(mt2060 tuner) DVB-T USB2.0' in warm state.<br>dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.<br>DVB: registering new adapter (Dposh(mt2060 tuner) DVB-T USB2.0)<br>
m920x_mt352_frontend_attach<br>DVB: registering frontend 0 (Zarlink MT352 DVB-T)...<br>m920x_mt2060_tuner_attach<br>MT2060: successfully identified (IF1 = 1220)<br>dvb-usb: Dposh(mt2060 tuner) DVB-T USB2.0 successfully initialized and connected.<br>
<br>so far so good :) , but when I scan with Kaffeine I get this:<br><br>Demod init! //this repeated ~ 30 times<br><br>mt352_read_register: readreg error (reg=3, ret==-110) //then this block or<br>mt2060 I2C write failed (len=2) //similar repeated until end of scan<br>
mt2060 I2C write failed (len=6)<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt2060 I2C read failed<br>
mt2060 I2C read failed<br>mt2060 I2C read failed<br>mt352_write() to reg 51 failed (err = -110)!<br>mt352_write() to reg 5e failed (err = -110)!<br><br><br>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?<br>
cheers for the help,<br>Andrew<br></div></div><br>