From: Rutger Hofman <rutger@cs.vu.nl>
To: linux-mtd@lists.infradead.org
Subject: Question on how NAND flash BBT is stored in the chip
Date: Thu, 16 Oct 2008 16:35:29 +0200 [thread overview]
Message-ID: <48F75131.9040002@cs.vu.nl> (raw)
Good afternoon list,
I have a question how the BBT (bad block table) is stored in MTD NAND
devices. I googled for a while, and browsed the code, but I am still not
sure.
The question:
Is the BBT stored/retrieved using a spare layout? Is ECC
generation/correction done for it?
This question derives from the question above: is the BBT marker pattern
stored within a spare layout (with slots for ECC, bad block markers
etc)? Or is it written verbatim (raw and unmangled) into the spare area?
If no ECC is used for the BBT, is that for a reason?
Thanks for the information,
Rutger Hofman
VU Amsterdam
next reply other threads:[~2008-10-16 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 14:35 Rutger Hofman [this message]
[not found] ` <7ccead5b0810170027h677520dav1ea09079175b93fe@mail.gmail.com>
2008-10-17 11:30 ` Question on how NAND flash BBT is stored in the chip Rutger Hofman
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=48F75131.9040002@cs.vu.nl \
--to=rutger@cs.vu.nl \
--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