Johannes Stezenbach wrote: > According to linux/Documentation/i2c/i2c-protocol.txt the correct > way to get a STOP condition between two I2C messages is send them > in seperate I2C transactions. I don't find this description in i2c-protocol. IMHO, it isn't possible to split a read request into a single write and a single read request outside of the core device. The device must be locked during both transfers. If the device isn't locked, it is possible that another transfer will change the slave offset before the content is read. This may occur with the current implementation. > If i2cdump is not able to handle > this, please fix i2cdump. > I2cdump deals with /dev/i2c and has nothing to do with this problem. - Hartmut _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb