public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: Pantelis Antoniou <panto@intracom.gr>, Srinivasu.Vaduguri@nokia.com
Cc: dwmw2@infradead.org
Cc: linux-mtd@lists.infradead.org
Cc: ddaney@avtrex.com
Subject: Re: [patch] Allow any filesystem on MTD Nand when Read Only
Date: Thu, 6 May 2004 10:02:25 +0200	[thread overview]
Message-ID: <200405061002.25973.tglx@linutronix.de> (raw)
In-Reply-To: <4099E739.4070803@intracom.gr>

On Thursday 06 May 2004 09:20, Pantelis Antoniou wrote:
> Maybe you can do something when writting your filesystem image when you
> detect
> a simple bit error you can immediately mark the block bad.
>
> How many times have you written the block in order for something like
> this to occur?
>
> It seems to me that when you have a read only partition the solution is
> to be
> carefull when writting your filesystem image.
> First you avoid the bad block altogether, and secondly you always bit
> verify the block. If the verify fails you immediately mark the block as bad
> and move
> on.
>
> I don't think that nandwrite does it though.

No it doesnt. This could be fixed easily.

-- 
Thomas
________________________________________________________________________
"Free software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech,'' not as in "free beer".
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2004-05-06  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AEB09EDA2548094C81ED6AA93269F63D01D09322@siebe001.apac.nokia.com>
2004-05-06  7:20 ` [patch] Allow any filesystem on MTD Nand when Read Only Pantelis Antoniou
2004-05-06  8:02   ` Thomas Gleixner [this message]
     [not found] <AEB09EDA2548094C81ED6AA93269F63D01D09323@siebe001.apac.nokia.com>
2004-05-06  9:39 ` Pantelis Antoniou
2004-05-06  9:48 ` Thomas Gleixner
2004-05-06  9:45   ` Pantelis Antoniou
2004-05-05 12:33 Pantelis Antoniou
2004-05-05 12:57 ` David Woodhouse
2004-05-05 13:03   ` Pantelis Antoniou
2004-05-05 15:26 ` David Daney
2004-05-05 17:44   ` Phillip Lougher
2004-05-05 19:07     ` David Daney
2004-05-06  7:12     ` Pantelis Antoniou

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=200405061002.25973.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Srinivasu.Vaduguri@nokia.com \
    --cc=dwmw2@infradead.org \
    --cc=panto@intracom.gr \
    /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