From: "Jörn Engel" <joern@logfs.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org, "Jörn Engel" <joern@logfs.org>,
"Gregory CLEMENT" <gclement00@gmail.com>
Subject: Re: Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ?
Date: Wed, 21 Nov 2007 18:15:02 +0100 [thread overview]
Message-ID: <20071121171501.GE20871@lazybastard.org> (raw)
In-Reply-To: <20071121105817.3adbfbb5@weaponx>
On Wed, 21 November 2007 10:58:17 -0600, Josh Boyer wrote:
> > 2007/11/21, Jörn Engel <joern@logfs.org>:
> > >
> > > What problem does the driver solve?
> > It allow to use cramfs/squashfs/fat in read-only on NAND flash for
> > embedded systems.
>
> Not really. It allows you to put one of those filesystems into
> NAND using a bad-block aware program initially, and mount it. It
> doesn't handle run-time bit flips or errors from what I can see.
Whether that is necessary I cannot tell. Maybe some people have
hardware where this isn't an issue.
But why yet another mtdblock driver? Is there a reason not to add the
required bits to mtdblock_ro.c?
Jörn
--
Correctness comes second.
Features come third.
Performance comes last.
Maintainability is easily forgotten.
next prev parent reply other threads:[~2007-11-21 17:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 14:27 Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ? Gregory CLEMENT
2007-11-21 16:08 ` Jörn Engel
2007-11-21 16:28 ` Gregory CLEMENT
2007-11-21 16:58 ` Josh Boyer
2007-11-21 17:07 ` Gregory CLEMENT
2007-11-21 17:13 ` Josh Boyer
2007-11-21 17:15 ` Jörn Engel [this message]
2007-11-21 17:32 ` Gregory CLEMENT
2007-11-21 17:43 ` Vitaly Wool
2007-11-21 17:45 ` Jörn Engel
2007-11-21 17:56 ` Vitaly Wool
2007-11-21 18:04 ` Jörn Engel
2007-11-23 14:35 ` Gregory CLEMENT
2007-11-23 14:45 ` Jörn Engel
2007-11-23 15:06 ` Gregory CLEMENT
2007-11-21 20:46 ` Ricard Wanderlof
2007-11-21 21:32 ` Jörn Engel
2007-11-21 22:33 ` Gregory CLEMENT
2007-11-21 22:54 ` Jörn Engel
2007-11-22 7:58 ` Ricard Wanderlof
2007-11-22 13:26 ` Jörn Engel
2007-11-23 7:42 ` Ricard Wanderlof
2007-11-23 8:18 ` Artem Bityutskiy
2007-11-23 9:08 ` Ricard Wanderlof
2007-11-23 9:21 ` Artem Bityutskiy
2007-11-23 9:28 ` Ricard Wanderlof
2007-11-23 18:40 ` David Brown
2007-11-26 9:42 ` Ricard Wanderlof
2007-11-26 13:58 ` Claudio Lanconelli
2007-11-23 8:19 ` Artem Bityutskiy
2007-11-23 12:46 ` Jörn Engel
2007-11-22 7:58 ` Ricard Wanderlof
2007-11-22 13:08 ` 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=20071121171501.GE20871@lazybastard.org \
--to=joern@logfs.org \
--cc=gclement00@gmail.com \
--cc=jwboyer@linux.vnet.ibm.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