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.....
------x--------
I've had a look at the code & have been attempting to add new code to the M920x driver to cope with the mt2060 tuner module, although all I've got to go on is the existing code for the qt1010 tuner. I'm not sure of 1 or 2 magic numbers like the i2c address & so on, and my C abilities are fairly limited, so I haven't managed to compile my new code without errors yet. I could do with some help ( or even a patch) to be honest
regards andrew
I've had a look at the code & have been attempting to add new code to the M920x driver to cope with the mt2060 tuner module, although all I've got to go on is the existing code for the qt1010 tuner. I'm not sure of 1 or 2 magic numbers like the i2c address & so on, and my C abilities are fairly limited, so I haven't managed to compile my new code without errors yet. I could do with some help ( or even a patch) to be honest
regards andrew
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
