From: Magnus Damm <damm@opensource.se>
To: Oliver Korpilla <okorpil@fh-landshut.de>
Cc: mgroeger@sysgo.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Initrd and PPCbug, can it work?
Date: Tue, 27 Apr 2004 15:39:08 +0200 [thread overview]
Message-ID: <20040427153908.4f1eeb8a.damm@opensource.se> (raw)
In-Reply-To: <408E55DD.7080806@fh-landshut.de>
On Tue, 27 Apr 2004 14:45:17 +0200
Oliver Korpilla <okorpil@fh-landshut.de> wrote:
> Use the initrd loaded with the kernel as a root filesystem in memory
> after bootup.
>
> Exactly what commandline parameters for the kernel would I need to make
> that?
I don't know what magic patches that are applied to the mvl-3.1 kernel
that a customer of mine use, but we use one kernel with initrd (ext2fs)
and nfs root + ip pnp support. Then we select at boot-time how we want
to boot the system:
Development: "noinitrd ip=on nfsroot=192.168.1.1:/home/nfs/foobar"
Standalone: "ip=off"
We boot a "Gzipped Multi-File Image" from u-boot, but I guess that booting
a standard zImage from anywhere would do too.
/ magnus
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-27 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 13:16 Initrd and PPCbug, can it work? okorpil
2004-04-26 22:09 ` Tom Rini
2004-04-27 6:39 ` Oliver Korpilla
2004-04-27 7:18 ` Marius Groeger
2004-04-27 8:50 ` Oliver Korpilla
2004-04-27 9:22 ` Marius Groeger
2004-04-27 9:42 ` Oliver Korpilla
2004-04-27 10:48 ` Magnus Damm
2004-04-27 12:42 ` Oliver Korpilla
2004-04-27 11:13 ` Marius Groeger
2004-04-27 12:45 ` Oliver Korpilla
2004-04-27 13:39 ` Magnus Damm [this message]
2004-04-27 16:17 ` Different solution Oliver Korpilla
2004-04-28 7:28 ` Oliver Korpilla
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=20040427153908.4f1eeb8a.damm@opensource.se \
--to=damm@opensource.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgroeger@sysgo.com \
--cc=okorpil@fh-landshut.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).