public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Steven Hein <ssh@sgi.com>
To: linux-mtd@lists.infradead.org
Subject: Erasing NAND bad blocks?
Date: Tue, 09 Aug 2005 11:41:33 -0500	[thread overview]
Message-ID: <42F8DCBD.2020407@sgi.com> (raw)

(Yes, I do know that erasing NAND flash blocks that are marked bad
is a VERY BAD IDEA.....I'm asking the question regarding a
specific HW/SW debug situation.......)

In the course of bringing up new hardware with NAND flash attached
I have had occasions where a software bug will cause a NAND-based
filesystem (such as YAFFS) to mark *all* of the blocks in a filesystem
as bad.  In the past, I have hacked the nand_erase() function to
allow erasing of bad blocks, then wrote a custom app to scan the OOB
data, doing a MEM_ERASE for blocks that had been marked bad by the FS.
Just wondering.....has anyone else
run into this situation, and is there a more graceful way of doing
this (i.e. without hacking the MTD NAND driver)?

Thanks!
Steve

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com)              Engineering Diagnostics/Software
Silicon Graphics, Inc.                          
1168 Industrial Blvd.                 Phone: (715) 726-8410
Chippewa Falls, WI 54729              Fax:   (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~	

             reply	other threads:[~2005-08-09 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 16:41 Steven Hein [this message]
2005-08-09 23:33 ` Erasing NAND bad blocks? Thomas Gleixner
2005-08-10 20:08   ` Charles Manning
2005-08-10 21:34     ` Sergei Sharonov
2005-08-10 21:38     ` Thomas Gleixner

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=42F8DCBD.2020407@sgi.com \
    --to=ssh@sgi.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