[linux-dvb] Dposh DVB-T USB2.0 seems to not work properly
websdaleandrew at googlemail.com
Tue Jun 24 11:20:25 CEST 2008
2008/6/24 Antti Palosaari <crope at iki.fi>:
> ma 23.6.2008 21:58 Andrew Websdale kirjoitti:
> > 2008/6/19 Antti Palosaari <crope at iki.fi>:
> >> Looks like small changes to m9206 driver is needed. MT2060 tuner needs
> >>>> IF1, i2c-address and output clock bit (0/1 if I remeber correctly..).
> >>>> Those can be seen from windows sniffs or by guessing / testing. IF1 is
> >>>> easy to set default one, 1220, wrong IF1 only decreases performance.
> >>>> If
> >>>> there is eeprom used then value is normally read from there, otherwose
> >>>> just set default. clock is easy to test. I don´t know how many
> >>>> i2c-address
> >>>> are supported by chip, but most probably there is not too many.
> >>>> Hopefully
> >>>> only 4. You can look from specs or from other drivers what
> >>>> i2c-addresses
> >>>> are used for mt2060. I think it will take 2-10 test to find correct
> >>>> values
> >>>> by trial and error method.
> >> 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()
> Sorry if I've made an obvious error, its the 1st time I've tried to change
> a driver, what should I be passing - is it "&adap->dev->i2c_adap"? I tried
> to find an example of mt2060 being attached, but I was barking up the wrong
> tree :). I don't want to waste your (or anyone elses) time, but I'd like to
> learn something about kernel drivers & maybe make some contribution if I
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the linux-dvb