From: Ivan Djelic <ivan.djelic@parrot.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Artem Bityutskiy" <dedekind1@gmail.com>,
"Matthieu Castet" <matthieu.castet@parrot.com>,
"Ricard Wanderlöf" <ricardw@axis.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Atlant Schmidt" <aschmidt@dekaresearch.com>,
"Brian Norris" <computersforpeace@gmail.com>
Subject: Re: dangerous NAND_BBT_SCANBYTE1AND6
Date: Thu, 26 May 2011 09:58:36 +0200 [thread overview]
Message-ID: <20110526075836.GD22192@parrot.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1105260907500.15966@lnxricardw.se.axis.com>
On Thu, May 26, 2011 at 08:09:15AM +0100, Ricard Wanderlof wrote:
>
> On Wed, 25 May 2011, Ivan Djelic wrote:
>
> >>> <digression> ...
> >>> And recent Micron devices do not store markers in flash; they just
> >>> return 0x00 for any byte read in a bad block (instead of the real
> >>> data), using an internal bad block table.
> >>> </digression>
> >> ...
> > Note that the usual bad block detection still works on those Micron devices.
> > They just do not store markers in flash.
> >
> > You can still mark a block gone bad either by writing your own marker into the
> > block or (better) in a separate BBT. The internal Micron table is hard-wired
> > and only used to shortcut access to factory bad blocks AFAIK.
>
> Does this also mean that if you for some reason screw up and mark lots of
> (good) blocks as bad, you can just erase all blocks in the flash; the
> factory-bad ones will refuse to be erased thanks to the on-chip bbt?
Exactly.
Ivan
next prev parent reply other threads:[~2011-05-26 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 15:52 dangerous NAND_BBT_SCANBYTE1AND6 Matthieu CASTET
2011-04-21 17:10 ` Ivan Djelic
2011-04-22 4:50 ` Brian Norris
2011-04-22 8:23 ` Artem Bityutskiy
2011-04-22 8:53 ` Matthieu CASTET
2011-04-22 9:28 ` Artem Bityutskiy
2011-04-21 17:33 ` Brian Norris
2011-04-22 9:02 ` Matthieu CASTET
2011-04-26 7:30 ` Ricard Wanderlof
2011-05-24 1:09 ` Brian Norris
2011-05-25 16:41 ` Ivan Djelic
2011-05-25 18:04 ` Atlant Schmidt
2011-05-25 18:31 ` Ivan Djelic
2011-05-26 7:09 ` Ricard Wanderlof
2011-05-26 7:58 ` Ivan Djelic [this message]
2011-05-26 7:07 ` Ricard Wanderlof
2011-05-26 7:57 ` Ivan Djelic
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=20110526075836.GD22192@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=aschmidt@dekaresearch.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
--cc=ricard.wanderlof@axis.com \
--cc=ricardw@axis.com \
/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;
as well as URLs for NNTP newsgroup(s).