From: "Thomas Gleixner" <tglx@linutronix.de>
To: linux-mtd@lists.infradead.org
Subject: Re: nand oob corruption recovery
Date: Thu, 1 Jul 2004 21:00:27 +0200 [thread overview]
Message-ID: <200407012100.28033.tglx@linutronix.de> (raw)
In-Reply-To: <40E448BD.8030909@cray.com>
On Thursday 01 July 2004 19:24, David Updegraff wrote:
> I realize that specs say that if you wipe out mfg. bad block markers
> that there is "no way to recover them".. but...
> Are there suggestions for plausibly reliable test sequences that one
> could run a nand chip thru to regenerate valid bad block markers?
>
> Presumeably, it is insufficient to simply try to erase all blocks,
> marking failures as bad... perhaps verified full page writes ?
Erasing may be not sufficient, as the block could be al ff. Writing all blocks
to all zeros and verify that it works. Maybe try a 0x55 and 0xAA pattern too.
--
Thomas
_____________________________________________________________________
From slash dot org
"When customers are visiting, engineers are not allowed to wear ties.
That way the customer can tell who is the engineer and who is the
salesman (and therefore whom to believe.). Ties cut off blood flow
to the brain, making it easier for the salesmen to do their jobs."
_____________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2004-07-01 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 17:24 nand oob corruption recovery David Updegraff
2004-07-01 19:00 ` Thomas Gleixner [this message]
2004-07-01 22:45 ` David Updegraff
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=200407012100.28033.tglx@linutronix.de \
--to=tglx@linutronix.de \
--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