From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Munir Bandukwala <munirb-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Writing to AT24C64C EEPROM fails on RHEL based kernels
Date: Mon, 7 Mar 2011 20:48:19 +0100 [thread overview]
Message-ID: <20110307194819.GA17883@pengutronix.de> (raw)
In-Reply-To: <4D753233.8060208-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
> 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?
> 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).
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-03-07 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 19:29 Writing to AT24C64C EEPROM fails on RHEL based kernels Munir Bandukwala
[not found] ` <4D753233.8060208-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org>
2011-03-07 19:48 ` Wolfram Sang [this message]
[not found] ` <20110307194819.GA17883-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-03-07 20:48 ` Munir Bandukwala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110307194819.GA17883@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=munirb-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.