From: "Si" <spse@secret.org.uk>
To: "Michael Rothwell" <rothwell@holly-springs.nc.us>, <spse@secret.org.uk>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Using JFFS2 as root FS on CF
Date: Wed, 28 Nov 2001 06:42:58 -0000 [thread overview]
Message-ID: <006d01c177d7$ee329190$0100a8c0@secret.org.uk> (raw)
In-Reply-To: 1006921285.9892.6.camel@gromit.house
Michael,
the latest blkmtd in CVS should fix the problem when compiled into the
kernel. you can then pass the kernel boot param
blkmtd_device=/dev/foo
Note, this version isnt yet it the latest kernel sources, but you should
just be able to get the one out of CVS and copy it
over the blkmtd.c in the kernel source tree.
I will hopefully send a patch off to the 2.4 maintainer later this week, I
didnt bother earlier as I assumed with the 2.4/2.5 change over, Linus and
Marcelo probably had more important bug fixes etc to deal with.
cheers
si
----- Original Message -----
From: "Michael Rothwell" <rothwell@holly-springs.nc.us>
To: "Michael Rothwell" <rothwell@holly-springs.nc.us>
Cc: <linux-mtd@lists.infradead.org>
Sent: Wednesday, November 28, 2001 4:21 AM
Subject: Re: Using JFFS2 as root FS on CF
> On Tue, 2001-11-27 at 22:42, Michael Rothwell wrote:
> > Does someone have a recipe for booting a kernel (2.4.13 or 2.4.16) with
> > this type of setup and having it mount the jffs2 fs as /?
>
>
> Addendum: blkmtd complains "error, missing 'device' name" -- I'm passing
> it in via lilo, but it looks like blkmtd doesn't read kernel arguments.
>
> -M
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
prev parent reply other threads:[~2001-11-28 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 3:42 Using JFFS2 as root FS on CF Michael Rothwell
2001-11-28 4:21 ` Michael Rothwell
2001-11-28 6:42 ` Si [this message]
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='006d01c177d7$ee329190$0100a8c0@secret.org.uk' \
--to=spse@secret.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=rothwell@holly-springs.nc.us \
/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