From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mark Ryden <markryde@gmail.com>
Cc: Justin Waters <justin.waters@timesys.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Creating an ext3 partition on an mtd device
Date: Thu, 27 Aug 2009 09:29:20 +0300 [thread overview]
Message-ID: <1251354560.3514.5.camel@localhost> (raw)
In-Reply-To: <dac45060908262259r2f5ff85tb2608bd02153e797@mail.gmail.com>
On Thu, 2009-08-27 at 08:59 +0300, Mark Ryden wrote:
> Hello, Justin,
> Thanks for your answer.
>
> Then why do I have in "Essential Linux Device Drivers" this , in
> "Block Device Emulation" section of chapter 17, "Memory Technology
> Devices" , this:
>
> Block Device Emulation
> The MTD subsystem provides a block driver called mtdblock that
> emulates a hard disk over flash memory. You can put any filesystem,
> say EXT2, over the emulated flash disk. Mtdblock hides complicated
> flash access procedures (such as preceding a write with an erase of
> the corresponding sector) from the filesystem. Device nodes created by
> mtdblock are named /dev/mtdblock/X, where X is the partition number.
> To create an EXT2 filesystem on the pda_fs partition of the handheld,
> as shown in Figure 17.2, do the following:
> bash> mkfs.ext2 /dev/mtdblock/2 Create an EXT2 filesystem
> on the second partition
>
> bash> mount /dev/mtdblock/2 /mnt Mount the partition
mtdblock does not do any bad block handling, so you cannot use it with
NAND. And it does not do any wear-leveling, and it has zero tolerance to
power cuts.
I think the text above assumes that you have NOR, you do not care about
WL and power-cuts.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-08-27 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 19:44 Creating an ext3 partition on an mtd device Mark Ryden
2009-08-26 21:26 ` Justin Waters
2009-08-27 5:59 ` Mark Ryden
2009-08-27 6:29 ` Artem Bityutskiy [this message]
2009-08-27 8:24 ` Jamie Lokier
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=1251354560.3514.5.camel@localhost \
--to=dedekind1@gmail.com \
--cc=justin.waters@timesys.com \
--cc=linux-mtd@lists.infradead.org \
--cc=markryde@gmail.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