From: Peter Horton <phorton@bitbox.co.uk>
To: linux-mtd@lists.infradead.org
Subject: Re: on-die ECC support
Date: Fri, 15 Mar 2013 17:58:47 +0000 [thread overview]
Message-ID: <51436157.5000609@bitbox.co.uk> (raw)
In-Reply-To: <CACwUX0O=_mXexe6RLgGznVThUdMiMFAEMdzdOWBdKxYa1pHcAQ@mail.gmail.com>
On 15/03/2013 16:08, David Mosberger-Tang wrote:
> We need to be able to support 4-bit-correcting ECC with a
> micro-controller that doesn't have hardware-support for that. We are
> planning to use the on-die ECC controller supported by Micron flash
> chips. I suppose we could use the BCH swecc support in the Linux
> kernel, but I'm concerned about the performance implication of that
> and we'd also have to add BCH ecc to our bootloader, which would mean
> more development and testing.
>
Be careful using the NAND status register to indicate bit flips. The
chips we were using set the status bit for any correction and this can
result in very high error counts. Some of the pages had bits which are
permanently 0 or 1 meaning they might need correction every read. We
worked around this by re-reading any page that the chip flagged as
corrected and using the software BCH to work out the actual number of
bits in error.
P.
next prev parent reply other threads:[~2013-03-15 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 16:08 on-die ECC support David Mosberger-Tang
2013-03-15 16:17 ` David Mosberger-Tang
2013-03-15 17:58 ` Peter Horton [this message]
2013-03-20 17:46 ` David Mosberger-Tang
[not found] <CACwUX0M-04vCTkA8WwNR9si=7N-xuYOTy6aWO7ty8xa1+S3rUw@mail.gmail.com>
2013-03-22 8:21 ` Peter Horton
2013-03-22 21:14 ` David Mosberger-Tang
2013-03-23 19:27 ` Peter Horton
-- strict thread matches above, loose matches on Subject: below --
2017-01-09 21:37 On-die " Peter Rosin
2017-01-09 21:46 ` Richard Weinberger
2017-01-10 14:54 ` Peter Rosin
2017-01-10 15:30 ` Richard Weinberger
2017-01-10 15:43 ` Boris Brezillon
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=51436157.5000609@bitbox.co.uk \
--to=phorton@bitbox.co.uk \
--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 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.