From: Thomas Gleixner <tglx@linutronix.de>
To: "William J. Beksi" <wjbeksi@setabox.com>, linux-mtd@lists.infradead.org
Subject: Re: bad block replacement
Date: Wed, 31 Mar 2004 08:15:38 +0100 [thread overview]
Message-ID: <200403310915.38528.tglx@linutronix.de> (raw)
In-Reply-To: <406A2A5F.7040005@setabox.com>
On Wednesday 31 March 2004 04:18, William J. Beksi wrote:
> 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.
The generic nand driver knows all about this. ECC is implemented and bad block
management is done in NAND aware filesystems.
Using cramfs on NAND is not really a good idea. Cramfs is _NOT_ aware of NAND
flash. There exist JFFS2 (compressing) and YAFFS (not compressing), which are
NAND aware. Use one of those and you are done with out any changes in the
code.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2004-03-31 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 2:18 bad block replacement William J. Beksi
2004-03-31 7:15 ` Thomas Gleixner [this message]
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=200403310915.38528.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=wjbeksi@setabox.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