On Mon, 4 Feb 2013 12:28:51 -0500, Neil Horman wrote: > I've got the same device on my system here. Seth, can you elaborate on what it > is. FWIW, I took a risk, read a block from that device and wrote the same block > back to it with my v6 driver, with dyamic debug enabled, and the reported > printk's indicated it succeded. That doesn't mean a thing, unfortunately. It is possible that the write did not work, if you attempted to write the same data as was already present, you can't tell the difference between success and failure. Some slave SMBus devices will ack all transactions regardless of whether they support these transactions or not. As long as we don't know what is this slave device at 0x54, it's impossible to tell if the driver really works. I am glad Seth could test it with a different, known slave device. > I'll test out this patch in a bit here, make > the other requested corrections and repost shortly. -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
