public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpc512x: Fix problem with I2C access before relocation
Date: Mon, 8 Jun 2009 18:48:50 +0200	[thread overview]
Message-ID: <200906081848.50593.sr@denx.de> (raw)
In-Reply-To: <20090608102501.A8037832E416@gemini.denx.de>

Hi Wolfgang,

On Monday 08 June 2009 12:25:01 Wolfgang Denk wrote:
> > This is needed for the upcoming esd MECP5123 board port which uses I2C
> > EEPROM for environment storage.
>
> Stefan, please  check  if  this  is  really  what  you  want  to  do.
> Environmentin EEPROM is *strongly* discouraged. It is slow like hell,
> and  even more unreliable. Do *not* do this. Check if you can use any
> other storage - NOR or NAND flash, or the like.

I know that EEPROM has some disadvantages. But this is not my choice but the 
customers (esd) decision. esd has used I2C EEPROM for environment storage for 
a long time and even included write-protection to the EEPROM.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  parent reply	other threads:[~2009-06-08 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:38 [U-Boot] [PATCH] mpc512x: Fix problem with I2C access before relocation Stefan Roese
2009-06-08 10:25 ` Wolfgang Denk
2009-06-08 10:33   ` Heiko Schocher
2009-06-08 16:44     ` Stefan Roese
2009-06-08 16:48   ` Stefan Roese [this message]
2009-06-08 18:05     ` Wolfgang Denk
2009-06-12 13:01 ` Wolfgang Denk

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=200906081848.50593.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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