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: off...@denx.de ===================================================================== _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot