From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200
Date: Tue, 23 Nov 2004 18:01:50 +0100 [thread overview]
Message-ID: <41A36CFE.9050900@imc-berlin.de> (raw)
In-Reply-To: <20041123165304.A4E1CC1430@atlas.denx.de>
Wolfgang Denk wrote:
> In message <41A35C81.20709@imc-berlin.de> you wrote:
>
>>Then I think CONFIG_INIT_CRITICAL is the best choice!
>
>
> Definitely not - CONFIG_INIT_CRITICAL is such an ugly name that I
> wonder who accepted a patch to introduce such a name ;-)
>
> There is no documentation what it does or means; there is not even a
> definitian what "sys-critical inits" might be - all the
> initializations are "system critical". This is bullsh*i.
>
> We should not use this name, but try to get rid of it.
Hmm. So I suggest replacing it with CONFIG_INIT_LOWLEVEL or CONFIG_LOWLEVEL_INIT.
But then: these init steps (clocks and memory) are vital for U-Boot to run. So
why do we need this define anyway if these steps should be done always... ?
--
Steven Scholz
next prev parent reply other threads:[~2004-11-23 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 14:11 [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Steven Scholz
2004-11-23 15:42 ` Steven Scholz
2004-11-23 16:42 ` Wolfgang Denk
2004-11-23 16:51 ` Steven Scholz
2004-11-23 17:18 ` Wolfgang Denk
2004-11-23 15:45 ` Wolfgang Denk
2004-11-23 15:51 ` Steven Scholz
2004-11-23 16:52 ` Wolfgang Denk
2004-11-23 17:01 ` Steven Scholz [this message]
2004-11-23 17:23 ` Wolfgang Denk
2004-11-24 12:54 ` Steven Scholz
2004-11-24 15:06 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 7:46 Friedrich, Lars
2004-11-24 10:26 ` Wolfgang Denk
2004-11-24 10:54 Paugam Luc
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=41A36CFE.9050900@imc-berlin.de \
--to=steven.scholz@imc-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.