On Fri, May 18, 2007, e9hack wrote: > > the stv0297 doesn't understand the repeated start condition on the > i2c-bus from a saa7146. The current frontend driver (stv0297.c) > handles this problem by splitting the read request into a write and a > read request. Other applications (e.g. i2cdump) are not able to read > the registers from the stv0297. The attached patch lets solve the > saa7146 this problem. If it is necessary, the driver inserts an > additional stop condition and moves the following start condition into > the next upload command for the saa7146. 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. If i2cdump is not able to handle this, please fix i2cdump. That said, I'm wondering why this state->config->stop_during_read cruft exists at all, as it should always be set to True? (I suspect that it's a misplaced kludge for the b2c2 driver.) Johannes _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
