From: "William J. Beksi" <wjbeksi@setabox.com>
To: linux-mtd@lists.infradead.org
Subject: bad block replacement
Date: Wed, 31 Mar 2004 10:18:07 +0800 [thread overview]
Message-ID: <406A2A5F.7040005@setabox.com> (raw)
I'm using a Samsung KM29U256T 32Mb nand flash with 4 partitions on a
cramfs. I'm trying to implement ECC and a method for replacing bad
blocks. The spare array consists of 16 bytes, positions 512-528, the
517th position being reserved for the bad block marker.
Can I arbitrarily pick where to store the 6 byte ECC code in the spare
array as long as I don't erase and/or overwrite the bad block marker?
Concerning the replacement of bad blocks, Samsung guarantees that the
1st or 2nd page of every invalid block has non-FFh data at the 517th
position of the array. They recommend keeping a table of valid/invalid
blocks.
When replacing blocks, should one start at the end of the flash and
replace a bad block with a good free block? How many free good blocks
should one typically allocate for the duration of the flash's life?
thank you
-Bill
next reply other threads:[~2004-03-31 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 2:18 William J. Beksi [this message]
2004-03-31 7:15 ` bad block replacement Thomas Gleixner
2004-03-31 7:26 ` Charles Manning
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=406A2A5F.7040005@setabox.com \
--to=wjbeksi@setabox.com \
--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