Hi Wilken, On Tue, 20 May 2008 14:15:04 +0200, Wilken Haase wrote: > Badly I don't know of anymore devices connected to this bus.
You could probe the bus using i2cdetect. Just testing if i2cdetect works will be a good test already. > I do have the datasheets and read them multiple times just to be sure. > The data sheet talks of needed delays. What does it say exactly? > I tried experimenting with udelay values at the right file and did slow > the bus down, both values up to 150. Note: values above 50 are not compatible with SMBus. > But while dumping the chip slowed noticeably > down i still got some bogus values back. Think that's maybe not the > right idea. > On another sidenote: I own another settopbox which is partly similar and > also uses a fs454 scan konverter, but controlled by an intel i830 chipset. > The fs454 is accessible without any problems there with the stock kernel > driver. I really don't think the bus is multi mastered. Maybe this is a > termination problem. If the other system works OK with basically the same type of hardware, then I indeed suspect a hardware defect on the failing box. Maybe try to find out someone else with exactly the same box which is failing for you, and see if it also fails for him/her? -- Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
