modprobe.conf help - multiple SAA7134 cards?
- From: hermann pitton <hermann-pitton (at) arcor.de>
- Date: Thu, 18 May 2006 22:07:02 +0200
Am Donnerstag, den 18.05.2006, 07:25 +0100 schrieb Ben Lancaster:
> > If Ben's dmesg is upon a cold boot I doubt. It could also be taken
> > after
> > some modules reload attempt. To avoid to introduce new, maybe
> > misleading
> > questions, Ben, can you try a cold boot, to be safe, let's say keep
> > the
> > machine for 30 seconds without any power connected, and tell us if the
> > the second card still reports the wrong eeprom content?
>
> Here you go...
>
> saa7134[0]: found at 0000:00:0c.0, rev: 1, irq: 18, latency: 32,
> mmio: 0xcfffb800
> saa7134[0]: subsystem: 185b:c900, board: Compro Videomate DVB-T300
> [card=70,insmod option]
> saa7134[0]: board init: gpio is 840500
> input: saa7134 IR (Compro Videomate DV as /class/input/input0
> saa7134[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2
> b2 92
> saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff
> ff ff
> saa7134[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 87 ff ff
> ff ff
> saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7134[0]: i2c eeprom 40: ff 02 00 c2 86 10 ff ff ff ff ff ff ff ff
> ff ff
> saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff cb
> saa7134[0]: i2c eeprom 60: 34 ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> tuner 0-0061: chip found (at) 0xc2 (saa7134[0])
> tuner 0-0068: chip found (at) 0xd0 (saa7134[0])
> tda9887 0-0043: chip found (at) 0x86 (saa7134[0])
> saa7134[0]: registered device video0 [v4l2]
> saa7134[0]: registered device vbi0
> saa7134[1]: found at 0000:00:0d.0, rev: 1, irq: 19, latency: 32,
> mmio: 0xcfffb400
> saa7134[1]: subsystem: 1850:0000, board: Compro Videomate DVB-T300
> [card=70,insmod option]
> saa7134[1]: board init: gpio is 840500
> input: saa7134 IR (Compro Videomate DV as /class/input/input1
> tuner 1-0061: chip found (at) 0xc2 (saa7134[1])
> tuner 1-0068: chip found (at) 0xd0 (saa7134[1])
> tda9887 1-0043: chip found (at) 0x86 (saa7134[1])
> 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
> DVB: registering new adapter (saa7134[0]).
> DVB: registering new adapter (saa7134[1]).
>
Hartmut was right. The subsystem trouble is already upon first
initialization. At least gpio on init is now the same.
Thanks,
Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list