From: Scott Wood <scottwood@freescale.com>
To: Nishanth Menon <menon.nishanth@gmail.com>
Cc: linux-mtd@lists.infradead.org, maragani2000@gmail.com
Subject: Re: nand_default_bbt and x8 large page nand devices
Date: Mon, 05 Jan 2009 14:31:26 -0600 [thread overview]
Message-ID: <49626E1E.1040408@freescale.com> (raw)
In-Reply-To: <782515bb0901051227k7c8b8a13o13016f0178058bf@mail.gmail.com>
Nishanth Menon wrote:
> I guess the real question could be: is this a bug in reality? Do all x8 large
> page devices expect 1 byte bb marker or is it just micron?
It's not so much a bug as just a wasted byte -- any good block should
contain all FFs from the factory, so unless software chooses to use it
for something else (or the controller insists on putting ECC there) it
should be harmless to treat the bad block marker as if it were two bytes.
-Scott
next prev parent reply other threads:[~2009-01-05 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 20:27 nand_default_bbt and x8 large page nand devices Nishanth Menon
2009-01-05 20:31 ` Scott Wood [this message]
2009-01-05 20:39 ` Nishanth Menon
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=49626E1E.1040408@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=maragani2000@gmail.com \
--cc=menon.nishanth@gmail.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