Hallo,
I found the MT2050 fixes... from Brett Gersekowski in the Mailing List
archive.
For me it seems that we can use the MT2050 the same way as MT2032, but
I cannot patch the 2.6-test11 sources to work with it. Did anyone do
it?
I tried the following:
--- ./drivers/media/video/tuner.c.orig 2003-12-06 18:24:46.000000000
+0100
+++ ./drivers/media/video/tuner.c 2003-12-06 18:50:08.000000000
+0100
@@ -305,7 +305,8 @@
}
// Look for MT2032 id:
// part= 0x04(MT2032), 0x06(MT2030), 0x07(MT2040)
- if((buf[0x11] != 0x4d) || (buf[0x12] != 0x54) || (buf[0x13] !=
0x04)) {+ if(((buf[0x11] != 0x4d) || (buf[0x12] != 0x54) || (buf
[0x13] != 0x04))
+ && ((buf[0x11] != 0x3c) || (buf[0x12] != 0xbf))) {
printk("not a MT2032.\n");
return 0;
}
So now it loads all the things it might need. Now modprobe bttv does
not print the message 'not a MT2032.' and it seems to do the
initialisation of the mt2032, which is now the mt2050 because of this
patch.
But I get the same errors as before:
mt2032: pll wait 1ms for lock (0xf0)
mt2032 Reg.E=0xf0
mt2032: pll wait 1ms for lock (0xf0)
mt2032 Reg.F=0x05
mt2032: re-init PLLs by LINT
MT2032 Fatal Error: PLLs didn't lock.
(Note: It prints out MT2032, but it's the MT2050 - I just didn't
rewrite all the strings for that.)
So whats wrong here?
Does anyone have a patch for the tuner.c for kernel 2.6-test11?
Martin
