[linux-dvb] Compro VideoMate DVB-T300 auto detect problem- suggested code fix

[James Lawrence]

On 30/03/2006, at 10:08 AM, Hartmut Hackmann wrote:

> Hi, all
>
> Mark Callaghan wrote:
>> James, Hartmut,
>> I have also had "interesting" PCI ID behaviour from my Compro  
>> VideoMate, on
>> FC4.
>> I have seen the correct PCI ID in dmesg, but I usually get  
>> 1850:0000 (or was
>> it 185b:0000?). I can't remember the exact ID. I've been using a
>> modprobe.conf workaround to get the saa7134-dvb module loaded.
>> My suspicion was that it was related to whether the machine was  
>> reset or
>> went through a power-down.
> That makes sense! Can you please verify this?
> I suspect that the board allows to remap the address of the eeprom  
> that
> defines the ID. This might be done i.e. with GPIOs of the SAA7134.
>

This shows the difference between a reset without removing power  
(warm boot) and a power down.

note: I have two carrds in my system, both report very similar  
results except that teh first is card 0 and the second is card 1. I  
have shown only card 1 below for convenience.

what is reported in dmesg as a result of executing modprobe saa7134  
after a warm boot:
saa7134[1]: found at 0000:02:09.0, rev: 1, irq: 217, latency: 32,  
mmio: 0xf6005000
saa7134[1]: subsystem: 1850:0000, board: UNKNOWN/GENERIC  
[card=0,autodetected]
saa7134[1]: board init: gpio is 843f00
saa7134[1]: i2c eeprom 00: 02 10 00 01 04 00 1c 00 40 03 00 10 04 00  
82 10
saa7134[1]: i2c eeprom 10: 00 e7 02 00 01 00 10 26 52 41 c0 06 f8 ed  
cb 00
saa7134[1]: i2c eeprom 20: 00 40 01 02 03 41 00 01 00 5e 00 06 40 e7  
32 00
saa7134[1]: i2c eeprom 30: 01 5f 20 77 ac 5e 00 88 53 71 32 8c c0 01  
0f 50
saa7134[1]: i2c eeprom 40: 26 02 00 00 02 00 67 00 00 50 51 2b 02 24  
66 2b
saa7134[1]: i2c eeprom 50: 00 24 67 50 70 e7 66 00 01 71 66 cc 03 50  
26 0b
saa7134[1]: i2c eeprom 60: 00 24 66 71 57 96 bc 9b 7f 38 57 05 0f 73  
58 a0
saa7134[1]: i2c eeprom 70: 57 38 57 7c 58 4e 9f 83 f2 ff 80 30 58 d5  
b8 14
saa7134[1]: registered device video1 [v4l2]
saa7134[1]: registered device vbi1

what is reported in dmesg as a result of executing modprobe saa7134  
after a cold boot:
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC2] -> GSI 17 (level,  
low) -> IRQ 217
saa7134[1]: found at 0000:02:09.0, rev: 1, irq: 217, latency: 32,  
mmio: 0xf6005000
saa7134[1]: subsystem: 185b:c900, board: Compro Videomate DVB-T300  
[card=70,autodetected]
saa7134[1]: board init: gpio is 843f00
input: saa7134 IR (Compro Videomate DV as /class/input/input4
tuner 1-0068: chip found @ 0xd0 (saa7134[1])
tda9887 1-0043: chip found @ 0x86 (saa7134[1])
saa7134[1]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2  
b2 92
saa7134[1]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff  
ff ff
saa7134[1]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 87 ff ff  
ff ff
saa7134[1]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff  
ff ff
saa7134[1]: i2c eeprom 40: ff 02 00 c2 86 10 ff ff ff ff ff ff ff ff  
ff ff
saa7134[1]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff  
ff cb
saa7134[1]: i2c eeprom 60: 34 ff ff ff ff ff ff ff ff ff ff ff ff ff  
ff ff
saa7134[1]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff  
ff ff
tuner 1-0068: tuner type not set
tuner 1-0068: tuner type not set
saa7134[1]: registered device video1 [v4l2]
saa7134[1]: registered device vbi1
NVRM: not using NVAGP, kernel was compiled with GART_IOMMU support!!
NVRM: not using NVAGP, kernel was compiled with GART_IOMMU support!!
tuner 1-0068: tuner type not set

Regards,
James.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20060330/1aec5a12/attachment.htm