From: Dominik Bozek <domino@mikroswiat.pl>
To: "Varlese, Christopher" <Christopher.Varlese@keymile.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Help: NOR flash MTD and JFFS2 rootfs
Date: Wed, 19 Nov 2008 14:44:54 +0100 [thread overview]
Message-ID: <49241856.1090209@mikroswiat.pl> (raw)
In-Reply-To: <D839955AA28B9A42A61B9181506E27C4013A03DC@SRVCHBER1212.ch.keymile.net>
Varlese, Christopher wrote:
> I'm having some trouble booting from a JFFS2 disk partition.
> I have a few questions maybe someone can help.
>
>
> Q1: mtdparts=x not necessary?
> U-Boot supports configuring and passing mtdparts=x in the kernel
> command line. But with powerpc the partitions can be defined in
> the device tree and the kernel can parse this to discover the MTD
> partitions. So is it right then I don't need to use mtdparts?
> ref: drivers/mtd/ofpart.c:of_mtd_parse_partitions()
>
If it is working, your choice.
> Q2: /proc/partitions empty?
> [...]
I can't explain.
>
> Q3: JFFS2 booting fails?
> I have a JFFS2 root fs disk image burned to a flash mtd partition.
> I can manually mount it with NFS/ram boot scenarios, but so far
> cannot boot directly from it as rootfs (infos below). Any
> good suggestions what might be wrong?
>
> [...]
> ...
> Kernel command line: root=/dev/mtdblock5 rw rootfstype=jffs2
> ip=192.168.33.38:192.168.33.35:192.168.33.35::eter1:eth0:off panic=1
> con0
> [...]
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
I'm using hexadecimal value for "root". I guess in your case try "root=1f05.
Domino
next prev parent reply other threads:[~2008-11-19 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 11:48 Help: NOR flash MTD and JFFS2 rootfs Varlese, Christopher
2008-11-19 13:44 ` Dominik Bozek [this message]
2008-11-19 14:02 ` Varlese, Christopher
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=49241856.1090209@mikroswiat.pl \
--to=domino@mikroswiat.pl \
--cc=Christopher.Varlese@keymile.com \
--cc=linuxppc-embedded@ozlabs.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