Hi ! On Tue, Apr 08, 2003 at 10:33:01PM -0700, Shaun Jackman wrote: > Here's a summary of the GPIO results so far. The only trend I see so > far, is that perhaps bit 12 (0x1000) indicates the presence of a > radio. I don't see any bit that Silvano, Shaun, and David all have in > common (besides 0x30000) to indicate the presence of IR. Speaking of > which, do we know how the IR module is connected to the FV card? Is > it on I2C, gpio, or somewhere else? > > Can everyone fill in this list with with > 2k v. 3k > radio v. no radio > IR v. no IR > EEPROM v. no EEPROM > > Cheers, > Shaun I'm not sure about what info is where, but my FV3K (radio,IR) looks like this: Linux video capture interface: v1.00 i2c-core.o: i2c core module saa7130/34: v4l2 driver version 0.2.7 loaded PCI: Found IRQ 5 for device 00:0a.0 saa7134[0]: found at 00:0a.0, rev: 1, irq: 5, latency: 32, mmio: 0xe1800000 saa7134[0]: subsystem: 5168:0138, board: LifeView FlyVIDEO3000 [card=2,autodetected] i2c-core.o: adapter saa7134[0] registered as adapter 0. saa7134[0]: i2c eeprom 00: 68 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff 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 i2c-core.o: driver i2c TV tuner driver registered. tuner: probing saa7134[0] i2c adapter [id=0x90000] tuner: chip found @ 0xc2 tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) i2c-core.o: client [Philips PAL_BG (FI1216 and compa] registered to adapter [saa7134[0]](pos. 0). saa7134[0]: registered device video0 [v4l2] saa7134[0]: registered device vbi0 saa7134[0]: registered device radio0 saa7134[0]/audio: audio carrier scan failed, using 5.500 MHz [default] Kernel 2.4.20, no patches, no special module-configuration. v4l2-20030318, saa7134-20030326 TV works, sound untested (I use reciever->soundcard), radio untested, IR untested. What other information do you need? HTH, rob
