From: Artem Bityutskiy <dedekind1@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Jason Lunz <lunz@acm.org>,
Denys Vlasenko <vda.linux@googlemail.com>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
David Woodhouse <dwmw2@infradead.org>,
atom ota <atomota@sleepyhammer.com>,
user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: allow mtd and jffs2 when ARCH=um
Date: Thu, 16 Dec 2010 17:18:31 +0200 [thread overview]
Message-ID: <1292512711.2364.85.camel@localhost> (raw)
In-Reply-To: <201012150031.21417.rob@landley.net>
On Wed, 2010-12-15 at 00:31 -0600, Rob Landley wrote:
> That is awesome and I'm not finding any documentation on it... Ah:
>
> http://wiki.maemo.org/Modifying_the_root_image#Block_device_emulating_an_MTD_device
>
> Wow that's awkward. Let's see, that says...
>
> mknod /tmp/mtdblock0 b 31 0
> modprobe loop
> losetup /dev/loop0 rootfs.jffs2
> modprobe mtdblock
> modprobe block2mtd
> # Note the ,128KiB is needed (on 2.6.26 at least) to set the
> # eraseblock size.
> echo "/dev/loop0,128KiB" > /sys/module/block2mtd/parameters/block2mtd
> modprobe jffs2
> mount -t jffs2 /tmp/mtdblock0 /media/jffs2
You should not need mtdblock in modern kernels, it is legacy. You should
be abole to mount jffs2 on top of mtd0 with
mount -t jffs2 mtd0 /media/jffs2
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-12-16 15:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22c797d00709272118i33d32b9dy93d5f5ec8f8edd30@mail.gmail.com>
[not found] ` <20071024011712.GA3762@falooley.org>
[not found] ` <1193208689.26096.48.camel@pmac.infradead.org>
2007-10-24 15:54 ` [PATCH] allow use of mtd and jffs2 on uml Jason Lunz
2007-10-24 16:24 ` atom ota
2007-12-27 18:15 ` Jason Lunz
2007-12-28 17:48 ` Sam Ravnborg
2010-12-07 7:29 ` [PATCH] mtd: allow mtd and jffs2 when ARCH=um Jason Lunz
2010-12-07 9:39 ` richard -rw- weinberger
2010-12-07 18:20 ` Jason Lunz
2010-12-14 16:24 ` Artem Bityutskiy
2010-12-14 19:51 ` Jason Lunz
2010-12-14 20:01 ` Artem Bityutskiy
2010-12-14 21:12 ` Geert Uytterhoeven
2010-12-14 21:23 ` Jason Lunz
2010-12-15 0:40 ` Rob Landley
2010-12-15 0:49 ` Rob Landley
2010-12-15 1:19 ` Jason Lunz
2010-12-15 6:31 ` Rob Landley
2010-12-16 15:18 ` Artem Bityutskiy [this message]
2010-12-18 4:08 ` Rob Landley
2010-12-19 17:08 ` Artem Bityutskiy
2010-12-15 8:18 ` Geert Uytterhoeven
2010-12-16 15:25 ` Artem Bityutskiy
2010-12-16 22:01 ` Anatolij Gustschin
2010-12-17 4:27 ` mtd: fix CONFIG_MTD_COMPLEX_MAPPINGS=n compile Jason Lunz
2010-12-19 16:47 ` Artem Bityutskiy
2010-12-19 19:07 ` Jason Lunz
2010-12-20 11:23 ` Artem Bityutskiy
2010-12-20 14:04 ` [PATCH] mtd: allow mtd and jffs2 when ARCH=um Jason Lunz
2010-12-22 14:40 ` Artem Bityutskiy
2011-01-06 15:45 ` David Woodhouse
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=1292512711.2364.85.camel@localhost \
--to=dedekind1@gmail.com \
--cc=atomota@sleepyhammer.com \
--cc=dwmw2@infradead.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lunz@acm.org \
--cc=richard.weinberger@gmail.com \
--cc=rob@landley.net \
--cc=sam@ravnborg.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=vda.linux@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).