From: Pete Popov <ppopov@embeddedalley.com>
To: " ªL«Ø¦w " <Mickey@turtle.ee.ncku.edu.tw>, linux-mips@linux-mips.org
Subject: Re: Is there any means to use Cramfs and JFFS2 images as root disks?
Date: Fri, 15 Oct 2004 10:45:42 -0700 (PDT) [thread overview]
Message-ID: <20041015174542.20487.qmail@web81008.mail.yahoo.com> (raw)
In-Reply-To: <002f01c4b2dc$cd1262e0$7101a8c0@dinosaur>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 853 bytes --]
--- ªL«Ø¦w <Mickey@turtle.ee.ncku.edu.tw> wrote:
>
> 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?
Yamon or any other bootloader doesn't have to support
jffs2 or cramfs. All it needs to do is pass the
parameters to the kernel. Your parameters above are
incorrect. rootfstype=jffs2 will not be recognized.
The /dev/mtdblock3 is fine, assuming that you really
do have a jffs2 fs there. Then, assuming that the
kernel has jffs2 statically compiled in, it will
recognize the FS and mount it.
Pete
next prev parent reply other threads:[~2004-10-15 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 17:31 Is there any means to use Cramfs and JFFS2 images as root disks? 林建安
2004-10-15 17:31 ` 林建安
2004-10-15 17:45 ` Pete Popov [this message]
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=20041015174542.20487.qmail@web81008.mail.yahoo.com \
--to=ppopov@embeddedalley.com \
--cc=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