Thanks Wolfram for your response, my comments are inline ...
On 03/07/2011 11:48 AM, Wolfram Sang wrote:
While looking for patches, I came accross
https://bugzilla.redhat.com/show_bug.cgi?id=182687 and adding an extra delay
in the piix4_transaction function fixes the problem for me as well.
So, this is not a problem anymore if I understand you correctly?
yes thats correct, I have to add a delay for the chip on my box (its not
the same as the one used in the patch above) and it works, what I was
wondering was why ubuntu/2.6.35 works without the additional delay or
any changes to code.
I think the problems are related, but any pointers would be appreciated. I am
pasting information about my machine, please let me know if you guys needs
any more information
This seems normal to me. The eeprom needs time to write the data. Any reasons
for not using the in-kernel eeprom driver (drivers/misc/eeprom/at24.c)? It
deals with all of that (and probably more).
I did try the at24 driver and had a similar issue, for ease of testing
and comparing different kernels, I switched to the user space code.
Regards,
Wolfram
--
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
