public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Gregory CLEMENT" <gclement00@gmail.com>
Cc: "Jörn Engel" <joern@logfs.org>, linux-mtd@lists.infradead.org
Subject: Re: Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ?
Date: Wed, 21 Nov 2007 11:13:02 -0600	[thread overview]
Message-ID: <20071121111302.67bc42c2@weaponx> (raw)
In-Reply-To: <305035a40711210907ib702394y55e832e57dc98b37@mail.gmail.com>

On Wed, 21 Nov 2007 18:07:19 +0100
"Gregory CLEMENT" <gclement00@gmail.com> wrote:

> 2007/11/21, Josh Boyer <jwboyer@linux.vnet.ibm.com>:
> > On Wed, 21 Nov 2007 17:28:05 +0100
> > "Gregory CLEMENT" <gclement00@gmail.com> wrote:
> >
> > > 2007/11/21, Jörn Engel <joern@logfs.org>:
> > > > On Wed, 21 November 2007 15:27:19 +0100, Gregory CLEMENT wrote:
> > > > >
> > > > > I come back with my question because it seems that last time I sent
> > > > > this mail mtd mailing list was done during few weeks, so maybe  this
> > > > > mail was lost.
> > > >
> > > > 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.
> >
> > josh
> >
> 
> Are these  run-time bit flips can happen on reading only mode?

They can, yes.  Particularly if you do lots of reads to the same NAND
page, which can happen for superblock type transactions.

josh

  reply	other threads:[~2007-11-21 17:13 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 [this message]
2007-11-21 17:15       ` Jörn Engel
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=20071121111302.67bc42c2@weaponx \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=gclement00@gmail.com \
    --cc=joern@logfs.org \
    --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