[linux-dvb] Any chance of help with v4l-dvb-experimental / Avermedia A16D please?

[Richard (MQ)]

Hi again all,

Mauro Carvalho Chehab wrote:
...
> Ok, the patch that fixed the callbacks were already applied.
> 
> For DVB to work, the demod needs to be initialized. From what I saw on
> bttv-gallery, this board uses an mt352 demod. Hopefully, it will use the same
> code as AV A16AR.
> 
> I'm enclosing an experimental patch that will enable DVB support for this
> board. Please test. 

Finally I have the A16D card in a working box, running OpenSuSE 10.3
FWIW (kernel 2.6.22.17). Sorry it took so long...

Starting from a virgin system (that is, current OpenSuSE rather than
vanilla) I did an hg clone followed by make, no errors. Next I took the
v27 firmware from your mail of 21st and then su -c "make install". Still
no errors, but it didn't work.

Next I added the patches mentioned above, one line was already present
("+	case SAA7134_BOARD_AVERMEDIA_A16D:" after line 5512) but they went
in with no other errors. Again, make was successful so installed and
re-booted.

dmesg extract follows:

> saa7130/34: v4l2 driver version 0.2.14 loaded
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
> PCI: setting IRQ 10 as level-triggered
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
> saa7133[0]: found at 0000:00:0a.0, rev: 209, irq: 10, latency: 32, mmio: 0xea002000
> saa7133[0]: subsystem: 1461:f936, board: AVerMedia Hybrid TV/Radio (A16D) [card=137,autodetected]
> saa7133[0]: board init: gpio is 32fa00
> saa7133[0]: i2c eeprom 00: 61 14 36 f9 00 00 00 00 00 00 00 00 00 00 00 00
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff 20 ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 01 00 08 ff 00 0e ff ff ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 40: ff 65 00 ff c2 1e 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
> tuner' 0-0061: chip found @ 0xc2 (saa7133[0])
> xc2028 0-0061: type set to XCeive xc2028/xc3028 tuner
> xc2028 0-0061: xc2028/3028 firmware name not set!
...
> xc2028 0-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
> xc2028 0-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000.
> (0), id 00000000000000ff:
> xc2028 0-0061: Loading firmware for type=(0), id 0000000100000007.
> SCODE (20000000), id 0000000100000007:
> xc2028 0-0061: Loading SCODE for type=SCODE HAS_IF_5640 (60000000), id 0000000200000007.
> xc2028 0-0061: Device is Xceive 3028 version 1.0, firmware version 2.7
> xc2028 0-0061: Device is Xceive 3028 version 1.0, firmware version 2.7
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11


So far so good, but nothing in /dev/dvb.

I read the correspondence with timf, don't think I missed anything?

I'd be very interested in your comments
-- 
Cheers
Richard (MQ)