[U-Boot-Users] U-Boot-NG ?
Grant Likely
grant.likely at secretlab.ca
Tue Jul 3 20:05:53 CEST 2007
On 7/3/07, Sascha Hauer <s.hauer at pengutronix.de> wrote:
> > I see a few approaches to handle this:
> > 1. eliminate console output from the wrapper. (by far the easiest,
> > but provides no clues when RAM configuration fails).
> > 2. cut down wrapper functionality in the wrapper (this is just early
> > boot after all). Eliminate printf() support in the wrapper and make
> > due with puts(). Reduce the wrapper console driver to output only.
> > The problem still remains that the env needs to be read to know how to
> > configure the console.
> > 3. Same as two; but don't read the environment. Use a static console
> > config instead.
>
> Do we really need console output before U-Boot has initialised SDRAM?
> For debugging some simple PUTC() and PUTHEX() macros would be
> sufficient. Of course they have to be disabled on systems designed to
> have a quiet console.
I think it is a good idea to at least default to spitting out
*something* on boot. Just in case RAM is hooped.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195
More information about the U-Boot
mailing list