ti 17.6.2008 22:29 Andrew Websdale kirjoitti: > 2008/6/12 Andrew Websdale >> 2008/6/12 Antti Palosaari <crope@xxxxxx>: >> wrote: >> >>> OK, then the reason might by tuner. Tuner may be changed to other one >>> or >>> tuner i2c-address is changed. I doubt whole tuner is changed. Now we >>> should >>> identify which tuner is used. There is some ways how to do that. >>> >>> 1) Look from Windows driver files >>> 2) Open stick and look chips >>> 3) Take USB-sniffs and try to identify tuner from there >> >> > I've opened the stick & there's an MT352 (as expected) but the other chip > is > an MT2060 which is the tuner, I think, as I see that there's an 'mt2060' > module in the tuner module directory. Is there some modification I can do > to > the code so that it gets picked up by the driver? - I know a bit of C++ > app > programming but I'm very new to C driver code, but would like to learn > more. > Hopefully I can help some others who have this chipset as well..... > regards Andrew 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 am now on holiday trip, but next week - monday or tuesday I can fix that driver that if anyone else haven´t done already. regards Antti _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
