From: 林建安 <Mickey@turtle.ee.ncku.edu.tw>
To: <linux-mips@linux-mips.org>
Subject: Is there any means to use Cramfs and JFFS2 images as root disks?
Date: Sat, 16 Oct 2004 01:31:20 +0800 [thread overview]
Message-ID: <002f01c4b2dc$cd1262e0$7101a8c0@dinosaur> (raw)
Hello,
I had successfully booted up Linux with an NFS root.
Trying to boot up Linux with Cramfs and JFFS2 roots, I am wondering how to
pass parameters to Kernel.
I found that on some bootloaders, parameters are like these:
rootfstype = jffs2 root=/dev/mtdblock3
But YAMON doesn't seem to support MTD BLOCK.
Therefore, how do I tell Kernel where the root image is on YAMON?
Thanks and regards,
Colin
WARNING: multiple messages have this Message-ID (diff)
From: 林建安 <Mickey@turtle.ee.ncku.edu.tw>
To: linux-mips@linux-mips.org
Subject: Is there any means to use Cramfs and JFFS2 images as root disks?
Date: Sat, 16 Oct 2004 01:31:20 +0800 [thread overview]
Message-ID: <002f01c4b2dc$cd1262e0$7101a8c0@dinosaur> (raw)
Message-ID: <20041015173120.rz0OY6MtSWy2uXowPoIgPg9OFriBmN05MPJyq0uJuVU@z> (raw)
Hello,
I had successfully booted up Linux with an NFS root.
Trying to boot up Linux with Cramfs and JFFS2 roots, I am wondering how to
pass parameters to Kernel.
I found that on some bootloaders, parameters are like these:
rootfstype = jffs2 root=/dev/mtdblock3
But YAMON doesn't seem to support MTD BLOCK.
Therefore, how do I tell Kernel where the root image is on YAMON?
Thanks and regards,
Colin
next reply other threads:[~2004-10-15 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 17:31 林建安 [this message]
2004-10-15 17:31 ` Is there any means to use Cramfs and JFFS2 images as root disks? 林建安
2004-10-15 17:45 ` Pete Popov
2004-10-16 3:04 ` Eugene Surovegin
[not found] ` <004201c4b331$f9f6b180$7101a8c0@dinosaur>
2004-10-16 16:45 ` Pete Popov
2004-10-16 17:41 ` ???
2004-10-16 17:41 ` ???
2004-10-16 22:04 ` Wolfgang Denk
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='002f01c4b2dc$cd1262e0$7101a8c0@dinosaur' \
--to=mickey@turtle.ee.ncku.edu.tw \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox