So far no response on this bug I reported about 2 weeks ago that includes a proposed fix. Could some one consider adding in the fix into the relevant tree? On 15 June 2011 08:33, Andrew Worsley <amworsley@xxxxxxxxx> wrote: > Hi, I have hit upon a bug in this driver in the 2.6.32 which caused > memory corrupt and crash in my kernel. It appears to be still present > in 3.0-rc3 http://thread.gmane.org/gmane.linux.drivers.i2c/8543 I have since identified the cause of the problem was the wrong clock frequency for the FPGA. I mis-understood the clock frequency to be the i2c bus frequency - but it is actually an FPGA clock frequency. Perhaps others will make the same mistake as well. In fact as it stands there is no module parameter to change your i2c bus frequency - other than by fiddling your FPGA clock frequency. Better would be a separate parameters for each with a clearer names. Andrew -- 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
