From: "Mark A. Greer" <mgreer@mvista.com>
To: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: boot/simple in ROM?
Date: Thu, 24 Apr 2003 11:02:40 -0700 [thread overview]
Message-ID: <3EA826C0.8050509@mvista.com> (raw)
In-Reply-To: <5.1.0.14.2.20030424134156.036e1e80@falcon.si.com>
Jerry Van Baren wrote:
>
> The "simple" boot loaders are loaders, they are NOT bootroms. They
> expect
> the board to have a firmware/bootrom/monitor that does the necessary very
> low level very hardware specific initialization (things like setting up
> memory maps, initializing the SDRAM controller, etc.). The "simple" boot
> loaders do the added steps necessary for starting linux, so they are
> necessary but NOT sufficient.
In general this is true. However, it is possible to put enough hw init
in the simple boot loader (bootwrapper as I and others now call it) to
run linux. This has been done in the past.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-24 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00032EDD.C22236@borg.org>
2003-04-24 17:44 ` boot/simple in ROM? Jerry Van Baren
2003-04-24 18:02 ` Mark A. Greer [this message]
2003-04-24 18:11 ` Basic Config file Kevin A. Sapp
[not found] ` <3EA82B56.3070808@ecubics.com>
2003-04-24 20:00 ` Kevin A. Sapp
2003-04-24 20:18 ` Wolfgang Denk
2003-04-25 12:53 boot/simple in ROM? Wells, Charles
2003-04-25 14:48 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 18:06 Kerl, John
2003-04-24 19:15 ` Kent Borg
2003-04-24 16:33 Kent Borg
2003-04-24 17:13 ` Dan Malek
2003-04-24 17:32 ` Kent Borg
2003-04-24 17:49 ` Mark A. Greer
2003-04-24 18:41 ` Dan Malek
2003-04-24 18:29 ` emanuel stiebler
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=3EA826C0.8050509@mvista.com \
--to=mgreer@mvista.com \
--cc=gerald.vanbaren@smiths-aerospace.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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.