From: tkoka <tkoka@shaw.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] handling of NAND blocks which go bad
Date: Thu, 14 Jul 2011 13:03:38 +0900 [thread overview]
Message-ID: <1310616218.8257.10.camel@localhost> (raw)
I have a question about how u-boot handles NAND blocks going bad over
time, for example when uncorrectable ECC errors or erase failures are
encountered for blocks which are not already in the Bad Block Table. I
know that u-boot properly skips already known bad blocks, but I can't
seem to find where new bad blocks are recorded in the BBT. Can anyone
point me in the right direction? Or confirm that this is not supported
in u-boot? I am using a BSP from Freescale on a custom mx25 board, but
I cannot find this handling in the latest u-boot git either.
TIA
next reply other threads:[~2011-07-14 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 4:03 tkoka [this message]
2011-07-14 9:40 ` [U-Boot] handling of NAND blocks which go bad Wolfgang Denk
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=1310616218.8257.10.camel@localhost \
--to=tkoka@shaw.ca \
--cc=u-boot@lists.denx.de \
/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.