Kirk Lapray wrote: > Thanks. > > You can use the changes to the get_dvb_firmware Perl script and then > run it (./get_dvb_firmware nxt2004) You will just have to copy it to > the correct location for your distribution, usually /lib/firmware. > You will also have to make sure you have "Hotplug firmware loading > support" enabled in your kernel. > > Let me know how it works. Heh... I should have known about that perl script... I saw it in the patch, but I totally forgot about it. Thanks. Here is what I have so far. Obviously I have to take a closer look at my programming, but I think I am done for tonight. ;-) Attached to this email is a patch containing my changes (for AVerTVHD a180) on top of yours. The nxt200x_set_ts_param inside saa7134-dvb.c is totally useless right now, as I haven't looked into methods of implementing this yet. This is what dmesg looks like right now, after running azap on a QAM256 channel: saa7130/34: v4l2 driver version 0.2.14 loaded ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 17 (level, low) -> IRQ 201 saa7133[0]: found at 0000:02:04.0, rev: 209, irq: 201, latency: 32, mmio: 0xfeaff000 saa7133[0]: subsystem: 1461:1044, board: AVerMedia AVerTVHD MCE A180 [card=75,autodetected] saa7133[0]: board init: gpio is 10400 tuner 3-0061: chip found @ 0xc2 (saa7133[0]) tuner 3-0063: chip found @ 0xc6 (saa7133[0]) saa7133[0]: i2c eeprom 00: 61 14 44 10 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 00 00 00 00 00 00 00 00 00 00 saa7133[0]: i2c eeprom 20: 01 40 01 02 02 ff 01 03 06 ff 01 11 00 00 00 00 saa7133[0]: i2c eeprom 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 saa7133[0]: i2c eeprom 40: ff 64 00 c2 14 16 ff ff 00 00 00 00 00 00 00 00 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 scan: found device @ 0x14 [???] saa7133[0]: i2c scan: found device @ 0x16 [???] saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] saa7133[0]: i2c scan: found device @ 0xc2 [???] saa7133[0]: i2c scan: found device @ 0xc6 [???] tuner 3-0061: tuner type not set tuner 3-0061: tuner type not set saa7133[0]: registered device video2 [v4l2] saa7133[0]: registered device vbi2 nxt200x: NXT2004 Detected DVB: registering new adapter (saa7133[0]). DVB: registering frontend 1 (Nextwave NXT200X VSB/QAM frontend)... nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)... nxt2004: Waiting for firmware upload(2)... nxt2004: Firmware upload complete nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xA6 nxt200x: Error reading multireg register 0xE6 nxt200x: Error reading multireg register 0xE6 ^^^^^^^^ This doesnt look like tuner trouble to me, although I believe tuner stuff is the most obvious thing that I might have wrong. Interestingly enough, these lines showed up for the first time: tuner 3-0061: chip found @ 0xc2 (saa7133[0]) tuner 3-0063: chip found @ 0xc6 (saa7133[0]) Those chips were hidden before I applied your v4l-kernel patch to my tree! Looks like your changes to tuner-simple somehow made these chips visible? Hmmm... I have to look into this further. Now, I should be able to tune analog tv using one of those. (I'll play around tomorrow.) For the nxt200x_config, I've tried pll addresses of 0x11 , 0x61 , and 0x63 ... all three produced the same results. I need to spend more time on it, but I thought I'd give you an update on what I have so far. The GPIO changes in saa7134-cards.c and the change in saa7134-ts.c were based on the original patch from Jean-Francois Thibert. Thanks. -Michael Krufky note to list readers: the attached patch is an expermintal, non-working patch. it is not intended for cvs inclusion. -------------- next part -------------- A non-text attachment was scrubbed... Name: avertvhd-dvb.patch Type: text/x-patch Size: 3828 bytes Desc: not available Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20051026/efd09c9b/avertvhd-dvb.bin
