From: "colin" <colin@realtek.com.tw>
To: "Ian Campbell" <icampbell@arcom.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [*VIP*] Re: Strange! Cannot use JFFS2 as root
Date: Thu, 21 Oct 2004 09:49:48 +0800 [thread overview]
Message-ID: <005201c4b710$448c9480$8b1a13ac@realtek.com.tw> (raw)
In-Reply-To: 1098282591.29412.1706.camel@icampbell-debian
Hi Ian,
Thank you. It works by your way.
I had already tried "root=1f:01" and it didn't work, and then I spent whole
day to test it... :-(
It seems that "root=1f01" and "root=31:01" are both acceptable.
Thanks and regards,
Colin
----- Original Message -----
From: "Ian Campbell" <icampbell@arcom.com>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-kernel@vger.kernel.org>
Sent: Wednesday, October 20, 2004 10:29 PM
Subject: [*VIP*] Re: Strange! Cannot use JFFS2 as root
> > I traced the code and found that when passing "/dev/mtdblock1" to
> > name_to_dev_t() in do_mounts.c, it would return 0 at every try_name(),
which
> > will fail at open() with the path "/sys/block/%s/dev".
> >
> > What's the problem? Could anyone tell me?
>
> If I remember correctly you need to pass the root in as the major and
> minor numbers for jffs2 on 2.6. For example my 2.6 command line is
> root=31:03 rootfstype=jffs2 ro console=ttyS0,115200
> rather that root=/dev/mtdblock3.
>
> I can't remember why this is the case though.
>
> Ian.
> --
> Ian Campbell, Senior Design Engineer
> Web: http://www.arcom.com
> Arcom, Clifton Road, Direct: +44 (0)1223 403 465
> Cambridge CB1 7EA, United Kingdom Phone: +44 (0)1223 411 200
>
next prev parent reply other threads:[~2004-10-21 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:03 Strange! Cannot use JFFS2 as root colin
2004-10-20 14:29 ` Ian Campbell
2004-10-21 1:49 ` colin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 14:02 colin
2004-10-20 16:30 ` Eugene Surovegin
2004-10-21 3:00 ` [*VIP*] " colin
2004-10-21 3:00 ` colin
[not found] ` <005601c4b719$ea253970$8b1a13ac@realtek.com.tw>
2004-10-21 4:07 ` Eugene Surovegin
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='005201c4b710$448c9480$8b1a13ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=icampbell@arcom.com \
--cc=linux-kernel@vger.kernel.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.