All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200
Date: Wed, 24 Nov 2004 13:54:33 +0100	[thread overview]
Message-ID: <41A48489.80203@imc-berlin.de> (raw)
In-Reply-To: <20041123172308.9BAE7C1430@atlas.denx.de>

Wolfgang Denk wrote:

> In message <41A36CFE.9050900@imc-berlin.de> you wrote:
> 
>>Hmm. So I suggest replacing it with CONFIG_INIT_LOWLEVEL or CONFIG_LOWLEVEL_INIT.
> 
> 
> Hmmm.. CONFIG or CFG? And what exactly is low (vs. high?) level here?
> 
> 
>>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... ?
> 
> 
> Good question. The only reason I can think of  is  to  allob  such  a
> two-stage boot loader as used by Atmel on the AT91RM9200DK.

So we check if all other arm920t boards have an implementation of memsetup(). 
Then kick out CONFIG_INIT_CRITICAL and introduce 
CONFIG_DO_NOT_MAKE_LOWLEVEL_INIT or something like that !? ;-)


-- 
Steven Scholz

  reply	other threads:[~2004-11-24 12:54 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
2004-11-23 17:23         ` Wolfgang Denk
2004-11-24 12:54           ` Steven Scholz [this message]
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=41A48489.80203@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.