From: Paul Radford <paul@radfordnz.net>
To: linux-mtd@lists.infradead.org
Subject: block2mtd booting impossible?
Date: Fri, 23 Jun 2006 00:14:54 +0900 [thread overview]
Message-ID: <449AB3EE.5000306@radfordnz.net> (raw)
Hi,
(Sorry to bother the devs but I can't find *any* info about this yet)
I have an x86 machine that up until 2.6.16.x was booting from JFFS2
filesystems via blkmtd (CF card in an IDE adapter). The kernel
parameters were:
ro root=/dev/mtdblock0 blkmtd_device=/dev/hda2,/dev/hda5,/dev/hda6
rootfstype=jffs2
That worked well. Is it possible to get the same functionality from
block2mtd (compiled in, not a module) now that blkmtd has been removed
in 2.6.17?
My attempt at doing so failed miserably:
ro root=/dev/mtdblock0 block2mtd=/dev/hda2 block2mtd=/dev/hda5
block2mtd=/dev/hda6 rootfstype=jffs2
I gave multiple block2mtd arguments because I don't see a
multiple-device capability in the code. Even with just one block2mtd
argument for the root FS, I just get the no-root panic. Am I missing
something here? Is JFFS2 block-device translation going to make the
whole block2mtd, mtdblock arrangement obsolete?
Thanks,
Paul
(please copy me in on replies - I'm not subscribed)
reply other threads:[~2006-06-22 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=449AB3EE.5000306@radfordnz.net \
--to=paul@radfordnz.net \
--cc=linux-mtd@lists.infradead.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