From: Kyungmin Park <kyungmin.park@samsung.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: John Smith <john.smith@arrows.demon.co.uk>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: UBI and OneNAND
Date: Tue, 07 Nov 2006 12:52:39 +0000 (GMT) [thread overview]
Message-ID: <32333290.224521162903965840.JavaMail.weblogic@ep_ml06> (raw)
Hi,
> > ##
> > ## Look at existing devices
> > ##
> > / # ls -l /dev/mtdblock?
> > brw-r----- 1 0 0 31, 0 Jan 1 00:00 /dev/mtdblock0
> > brw-r----- 1 0 0 31, 1 Jan 1 00:00 /dev/mtdblock1
> > brw-r----- 1 0 0 31, 2 Jan 1 00:00 /dev/mtdblock2
> > brw-r----- 1 0 0 31, 3 Jan 1 00:00 /dev/mtdblock3
> 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.
I can't mount with name but It's possible with new mtdblock node
mtd = 3 -> mtd > 7
# mount -t jffs2 /dev/mtdblock7 /mnt
I will send more detailed description tomorrow.
Thank you,
Kyungmin Park
next reply other threads:[~2006-11-07 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 12:52 Kyungmin Park [this message]
2006-11-08 16:09 ` UBI and OneNAND Artem Bityutskiy
-- 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=32333290.224521162903965840.JavaMail.weblogic@ep_ml06 \
--to=kyungmin.park@samsung.com \
--cc=dedekind@infradead.org \
--cc=john.smith@arrows.demon.co.uk \
--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