linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Munir Bandukwala <munirb-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Munir Bandukwala
	<Munir.Bandukwala-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org>,
	"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Writing to AT24C64C EEPROM fails on RHEL based kernels
Date: Mon, 07 Mar 2011 12:48:39 -0800	[thread overview]
Message-ID: <4D7544A7.3090509@riverbed.com> (raw)
In-Reply-To: <20110307194819.GA17883-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

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
>

      parent reply	other threads:[~2011-03-07 20: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
     [not found]     ` <20110307194819.GA17883-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-03-07 20:48       ` Munir Bandukwala [this message]

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=4D7544A7.3090509@riverbed.com \
    --to=munirb-dueqmywuh4dwk0htik3j/w@public.gmane.org \
    --cc=Munir.Bandukwala-DUeqMYwuH4dWk0Htik3J/w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).