From: Bill Gatliff <bgat@billgatliff.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Can ID the NAND chip, but every erase block is bad?
Date: Sun, 03 Jan 2010 07:58:18 -0600 [thread overview]
Message-ID: <4B40A27A.30804@billgatliff.com> (raw)
In-Reply-To: <1262426622.3181.5832.camel@macbook.infradead.org>
David Woodhouse wrote:
> Take a closer look at how bad blocks were detected under 2.6.20.
>
> A virgin chip will use a certain byte in the spare area of each
> eraseblock to mark that block as bad. But often we reclaim those bytes
> and transcribe the information into a bad block table elsewhere on the
> flash.
>
> Booting a kernel which ignores the bad block table and looks for the bad
> block markers in the original location will have fairly much the effect
> you describe.
>
Ok, I'll take a look into that code.
Is there any way to instruct MTD to discard any previous bad block
information, and reconstruct the bad block table from scratch?
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat@billgatliff.com
next prev parent reply other threads:[~2010-01-03 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 5:05 Can ID the NAND chip, but every erase block is bad? Bill Gatliff
2010-01-02 10:03 ` David Woodhouse
2010-01-03 13:58 ` Bill Gatliff [this message]
2010-01-03 15:44 ` Darwin Rambo
2010-01-03 15:55 ` David Woodhouse
2010-01-04 19:48 ` Bill Gatliff
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=4B40A27A.30804@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=dwmw2@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.