Hi, I have a Compro DVB-T220 card which I'm trying to get working on openSUSE 10.2 + vanilla 2.6.22. Looking at Compro website it seems like it's almost identical to the T100 which does not have the tuner screen can, remote wake and has a smaller remote. Best card pictures are on: http://www.comprousa.com/New/en/product/t100t220/t100-Features.html http://www.comprousa.com/New/en/product/t100t220/t220-Features.html Daniel Paull posted this about T100: http://www.mail-archive.com/linux-dvb@xxxxxxxxxxx/msg23212.html As my T220 has an saa7130hl and mt352, and in light of above, I assumed the T220 uses a qt1010 also, hidden under the can. I hacked around with some source code to add a T220 card ID and get the saa7134-dvb.c code to dvb_attach an mt352 and a qt1010. The mt352 and qt1010 code seem happy that they've found their devices and added printk's show that they're being read / written to OK on load and dvbscan. Doing a dvbscan gives "tuning failed" messages. I didn't expect a miracle from my hacks and I'm in need of some info. / guidance. Looking at the mt352 datasheet gives no info. re. programming this. As the mt352 code obviously does this, where did the info. come from? Also the qt1010: I can't even get a chip data sheet on the web. The qt1010 code looks like some clever reverse engineering has been going on. If this is the case, don't the chip mfrs or Compro help? >From what little info. is on the mt352 datasheet it looks like it can take clever control of the tuner via secondary I2C rather than having it on the 7130 bus. I don't know if that's what the ".no_tuner = 1," config. option changes but with it set I get qt1010 printk output at every tune attempt (in addition to mt352) rather than just at the start of dvbscan. Here's some dmesg O/P from my hacks. Included are "mt352_*" and "qt1010_*" from my printk's but I left out the later ones resulting from the "mt352_*_init": saa7130/34: v4l2 driver version 0.2.14 loaded saa7130[0]: found at 0000:03:0a.0, rev: 1, irq: 21, latency: 64, mmio: 0xfeaffc00 saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected] saa7130[0]: board init: gpio is 840000 input: saa7134 IR (Compro Videomate DV as /class/input/input5 saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: Reconfigured board as Compro Videomate DVB-T220 saa7130[0]: registered device video0 [v4l2] saa7130[0]: registered device vbi0 mt352_attach mt352_read_register 7f 13 qt1010_attach qt1010_readreg 29 39 Quantek QT1010 successfully identified. DVB: registering new adapter (saa7130[0]). DVB: registering frontend 0 (Zarlink MT352 DVB-T)... I am an electronic eng. with a reasonable bit of programming exp. Can I help this along? Is it a big job to add support for T220(T100?)? What's involved? I have no clue re. tuner / demod operation / programming methods and without the info. / understanding the driver developers obviously have there's nothing more I can do a this stage. Regards, Murray _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
