Hi, on an i.MX31-based system I observe a strange effect:
cat /sys/class/i2c-adapter/.../eeprom > /tmp/e1 rmmod <adapter-driver> modprobe <adapter-driver> cat /sys/class/i2c-adapter/.../eeprom > /tmp/e2 after which the first 0x40 bytes in e2 are zero. The rest is correct - as in e1. To recover I have to rmmod eeprom i2cdetect ... # incluging eeprom addresses modprobe eeprom I would suspect a software bug, but I get this with two alternative adapter drivers (mxc and imx - see my recent post to the list), and on a laptop with 2.6.26 I don't get this. The kernel on i.MX31 is a pretty fresh linux-next. Does this look like a hardware "feature"? Or do we have a regression? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
