From: jasmine@linuxgrrls.org
To: Esben Nielsen <ESN@vestas.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Booting from DOC Millenium
Date: Mon, 11 Oct 2004 11:16:11 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.60.0410111114030.13309@hex.linuxgrrls.org> (raw)
In-Reply-To: <98223556A08BA64E8C969246704EEE3B17FE85@aarexch01.vws.vestas.dom>
On Mon, 11 Oct 2004, Esben Nielsen wrote:
> 1) Have a small bootsector and used a compressed kernel in the 1Mb NOR.
This is a common strategy.
> 2) Get a bootsector which can read the kernel from the filesystem on the
> DOC. Is there any such bootsector anywhere?
GRUB can do this. If you're on a non-Intel platform, there are other
bootloaders that could be persuaded to do this.
> 3) Go for a 3 stage boot: Have a small bootsector which boots a small,
> never changed Linux kernel from the 1Mb NOR. That small kernel does
> one thing: read out the real kernel from the DOC. Do anyone have
> experience with such a strategy?
LinuxBIOS does this.
> 4) Use a small Linux as a bootsector. Compile the initial hardware setup
> in before decompression and instead of starting initrd make something
> like "kexec" to start the real, runtime kernel. Has anyone been
> playing with this?
...that's functionally the same as (3) above.
> Having to have a seperate bootsector for Linux is not very good. We
> otherwise use VxWorks here.
Grub et al. can boot VxWorks.
-J.
prev parent reply other threads:[~2004-10-11 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 9:56 Booting from DOC Millenium Esben Nielsen
2004-10-11 10:16 ` jasmine [this message]
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=Pine.LNX.4.60.0410111114030.13309@hex.linuxgrrls.org \
--to=jasmine@linuxgrrls.org \
--cc=ESN@vestas.com \
--cc=linux-mtd@lists.infradead.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.