From: Artem Bityutskiy <dedekind@infradead.org>
To: kyungmin.park@samsung.com
Cc: John Smith <john.smith@arrows.demon.co.uk>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI and OneNAND
Date: Wed, 08 Nov 2006 18:09:20 +0200 [thread overview]
Message-ID: <1163002160.3800.8.camel@sauron> (raw)
In-Reply-To: <32333290.224521162903965840.JavaMail.weblogic@ep_ml06>
Hello,
On Tue, 2006-11-07 at 12:52 +0000, Kyungmin Park wrote:
> > Yo do not need mtdblock devices to mount JFFS2 at all. JFFS2 anyway
> > works with MTD devices directly and this is just an old way to mount
> > JFFS2. /dev/mtdX are character devices and you cannot feed the mount
> > utility by character devices, so this is why fake block devices were
> > used. Nowadays there is device-less mount support and you may use:
>
> > mount mtd7 /mnt/nvm
>
> Yes, I can mount ubi with avobe method.
The device-less mount I described is a feature of *JFFS2*. It does not
depend on if there is UBI or not.
You are just trying to do an incorrect thing.
It is similar to LVM - you feed hard drives to LVM, then create LVM
volumes, then mount those LVM volumes, not the hard drives. Similar in
case of UBI. You feed mtd3 to UBI, then you create UBI volumes which are
also accessible as emulated MTD devices, and you mount _those_ MTD
devices.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-11-08 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 12:52 UBI and OneNAND Kyungmin Park
2006-11-08 16:09 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-07 2:35 박경민
2006-11-07 8:50 ` Frank Haverkamp
2006-11-07 10:20 ` John Smith
2006-11-07 11:39 ` Artem Bityutskiy
2006-11-07 11:47 ` Josh Boyer
2006-11-07 14:10 ` Artem Bityutskiy
2006-11-07 14:24 ` Josh Boyer
2006-11-07 14:39 ` Artem Bityutskiy
2006-11-07 9:16 ` Artem Bityutskiy
2006-11-08 16:03 ` Artem Bityutskiy
2006-11-04 8:22 UBI and OneNand John
2006-11-06 9:46 ` Frank Haverkamp
2006-11-06 13:18 ` Artem Bityutskiy
2006-11-06 20:16 ` John Smith
2006-11-06 20:54 ` Josh Boyer
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=1163002160.3800.8.camel@sauron \
--to=dedekind@infradead.org \
--cc=john.smith@arrows.demon.co.uk \
--cc=kyungmin.park@samsung.com \
--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