From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Fri, 17 Jul 2009 13:46:13 +0200
Subject: [U-Boot] [PATCH] Add "cpu_config" command for PPC4xx bootstrap
	configuration
In-Reply-To: <20090717114050.9C51D832E416@gemini.denx.de>
References: <1247822763-20761-1-git-send-email-sr@denx.de>
	<200907171326.25645.sr@denx.de>
	<20090717114050.9C51D832E416@gemini.denx.de>
Message-ID: <200907171346.13218.sr@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.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
=====================================================================