From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Brian Norris <norris@broadcom.com>
Subject: dangerous NAND_BBT_SCANBYTE1AND6
Date: Thu, 21 Apr 2011 17:52:59 +0200 [thread overview]
Message-ID: <4DB052DB.7040308@parrot.com> (raw)
Hi,
I believe NAND_BBT_SCANBYTE1AND6 behavior is very dangerous.
We have a ST flash where ecc where but on bit 5 and 6.
With new kernel all block are bad.
Is this option is really needed ?
ST datasheet say [1]. We already check the first Word.
Why do we need to check the 6th Byte ?
Matthieu
PS : the code check 1st, 2nd, 6th, 7th Bytes. So it check too much bytes.
[1]
The devices are supplied with all the locations inside valid blocks erased
(FFh). The Bad
Block Information is written prior to shipping. Any block, where the 1st and 6th
Bytes, or 1st
Word, in the spare area of the 1st page, does not contain FFh, is a Bad Block.
next reply other threads:[~2011-04-21 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 15:52 Matthieu CASTET [this message]
2011-04-21 17:10 ` dangerous NAND_BBT_SCANBYTE1AND6 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
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=4DB052DB.7040308@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=norris@broadcom.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).