From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add "cpu_config" command for PPC4xx bootstrap configuration
Date: Fri, 17 Jul 2009 13:46:13 +0200 [thread overview]
Message-ID: <200907171346.13218.sr@denx.de> (raw)
In-Reply-To: <20090717114050.9C51D832E416@gemini.denx.de>
On Friday 17 July 2009 13:40:50 Wolfgang Denk wrote:
> > > But would it not be useful to be able to detect any "illegal"
> > > settings, for example resulting from accidentyial corruption of the
> > > EEPROM data?
> >
> > I don't understand this. How should the code detect an "illegal" setting?
> > All settings configured in the board specific code are valid.
>
> You define a list of ppc4xx_config_count known configuration
> settings; the data read from the EEPROM either matches one of these
> then it is a "known" or "legal" setting, or it does not - in that
> case the EEPROM contains an "illegal" setting. This should at least
> trigger a warning message (probably including the hex values as read
> from the EEPROM).
Ah, yes. Good idea. Will add.
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
=====================================================================
prev parent reply other threads:[~2009-07-17 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 9:26 [U-Boot] [PATCH] Add "cpu_config" command for PPC4xx bootstrap configuration Stefan Roese
2009-07-17 9:32 ` Stefan Roese
2009-07-17 9:51 ` Eibach, Dirk
2009-07-17 10:45 ` Wolfgang Denk
2009-07-17 11:13 ` Stefan Roese
2009-07-17 11:20 ` Wolfgang Denk
2009-07-17 11:26 ` Stefan Roese
2009-07-17 11:40 ` Wolfgang Denk
2009-07-17 11:46 ` Stefan Roese [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=200907171346.13218.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