On Monday 12 September 2005 00:06, Paul V. Gratz wrote:
> gratz1 ~ # i2cdetect -a 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 0x00-0x7f.
> Continue? [Y/n] y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 40: XX XX XX UU XX XX XX XX XX XX XX XX XX XX XX XX
> 50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>
> I'm not sure I totally understand this output but if I'm guessing correctly
> it looks like on bus 0 we have addresses 0x1b,0x43,0x50,0x60 and 0x61. On
> bus1 we have 0x1b,0x43,0x50, and 0x61. Does look right?
Everything is accounted for except for address 0x44 (cx25840). Are you sure
your card works? Can you test on a Windows system? I'm strongly beginning to
suspect a hardware problem. Perhaps the cx24850 chips are simply broken or
the I2C wires are broken.
Hans
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
