Hi Avl, Am Donnerstag, den 10.09.2009, 21:51 +0000 schrieb Avl Jawrowski: > hermann pitton <hermann-pitton <at> arcor.de> writes: > > > If it seems to deliver stable results now, you can even try to re-flash > > it with rewrite_eeprom.pl in v4l2-apps/util. Read the instructions on > > top of it. > > With 2.6.30 it's stable. I've reflashed the eeprom and now the card is > autodetected: because of other obligations I do only follow loosely what happens on the list. Don't expect me at latest. > saa7130/34: v4l2 driver version 0.2.15 loaded > saa7133[0]: found at 0000:01:02.0, rev: 209, irq: 22, latency: 32, mmio: > 0xcfddf800 > saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i > [card=101,autodetected] > saa7133[0]: board init: gpio is 600e000 > IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs > saa7133[0]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 > saa7133[0]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2e 15 13 ff ff > saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e7 ff 21 00 c2 > saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff 15 0e 6c a3 eb 03 c5 e8 9d > saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > i2c-adapter i2c-0: Invalid 7-bit address 0x7a > tuner 0-004b: chip found @ 0x96 (saa7133[0]) > tda829x 0-004b: setting tuner address to 61 > tda829x 0-004b: type set to tda8290+75a > saa7133[0]: registered device video0 [v4l2] > saa7133[0]: registered device vbi0 > saa7133[0]: registered device radio0 > dvb_init() allocating 1 frontend > DVB: registering new adapter (saa7133[0]) > DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)... > tda1004x: setting up plls for 48MHz sampling clock > tda1004x: found firmware revision 29 -- ok It is important to reflash it with your _original_ eeprom stuff on the long run, for now it does not matter. I see at least three different eeprom contents for now, might make a difference for LNA activation or for external voltage to an active antenna, also seven different remotes are listed, one marked as dysfunctional currently on the m$ driver ... > However it works still only with Kaffeine and w_scan. > dvbscan (last mercurial) give: Off hand I can't tell, but try with "scan". I did not use "dvbscan" since years and can't tell the status. > Unable to query frontend status > > And with 2.6.31 (same configuration) appears this new error: > > i2c-adapter i2c-0: Invalid 7-bit address 0x7a > > It can be a problem? No, it is only related to the first i2c remote on the Upmost Purple TV. It is unlikely that anybody is on the list with such a card currently. Likely it means we should shift it >> 1. Cheers, Hermann -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
