On Sat, 2008-09-13 at 23:07 -0400, Rick wrote: > Here are the results of the i2cdetect: > > i2c-5 i2c NVIDIA i2c adapter I2C adapter > i2c-4 i2c NVIDIA i2c adapter I2C adapter > i2c-3 i2c NVIDIA i2c adapter I2C adapter > i2c-2 i2c ivtv i2c driver #1 I2C adapter > i2c-1 smbus SMBus Via Pro adapter at 5000 SMBus adapter > i2c-0 i2c ivtv i2c driver #0 I2C adapter > > i2cdetect 2 0x70 0x71 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/2. > I will probe address range 0x70-0x71. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: > 10: > 20: > 30: > 40: > 50: > 60: > 70: -- --
OK. Your second card doesn't have anything responding on the addresses that the Z8 firmware should be responding to. It likely means that the chip isn't there, but it could also mean the chip is there and just needs a reset sequence. > > i2cdetect 1 0x70 0x71 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/1. > I will probe address range 0x70-0x71. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: > 10: > 20: > 30: > 40: > 50: > 60: > 70: -- -- You probed the wrong I2C bus. Your first ivtv card's bus is i2c-0 not i2c-1 according to the dump at the top of the e-mail. This result is invalid. > I threw this in for good measure: > i2cdetect 0 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/0. > I will probe address range 0x03-0x77. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- > 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: UU UU 72 73 -- -- -- -- OK. This is the bus on your first ivtv card. 70 & 71 were skipped because lic_pvr150 has probably registered them. Addresses 72 and 73 are addresses the Z8 firmware will also respond to for other functions. There is definitely a Z8 microcontroller on this board. But you knew that... :) > > i2cdetect 1 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/1. > I will probe address range 0x03-0x77. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2f > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: 50 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- Not an ivtv i2c bus. This doesn't matter. > And finally: > i2cdetect 2 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/2. > I will probe address range 0x03-0x77. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- > 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- This strongly indicates that there is no Z8 chip on the board. It could also indicate that it is there, but not responding for some reason. You'll need to do a visual inspection or write a small program to stimulate the ivtv driver's private ioctl() for resetting the Z8 IR chip. BTW: 50 is the eeprom 61 is the tuner 44 is the broadcast decoder 1b is the baseband audio mux Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
