From: Peter Horton <phorton@bitbox.co.uk>
To: David Mosberger-Tang <dmosberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: on-die ECC support
Date: Fri, 22 Mar 2013 08:21:15 +0000 [thread overview]
Message-ID: <514C147B.3030609@bitbox.co.uk> (raw)
In-Reply-To: <CACwUX0M-04vCTkA8WwNR9si=7N-xuYOTy6aWO7ty8xa1+S3rUw@mail.gmail.com>
On 21/03/2013 20:00, David Mosberger-Tang wrote:
>
> I missed your email until now. You said:
>
> > 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.
>
> Ouch. I think you are right: it looks to me that the chip sets the
> REWRITE_RECOMMENDED bit
> for any bit flips. Is the Linux BCH code compatible with the Micron code?
>
> Yes, using software BCH to figure out actual number of bitflips would
> be the right approach then.
> Is there a patch for that somewhere?
Not a patch but the driver file is here :-
http://files.bitbox.co.uk/public/nand-on-die-ecc/10CUL494_nand_2.6.37.c
Credit for the Micron ECC layout goes to Ivan Djelic IIRC.
P.
next parent reply other threads:[~2013-03-22 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACwUX0M-04vCTkA8WwNR9si=7N-xuYOTy6aWO7ty8xa1+S3rUw@mail.gmail.com>
2013-03-22 8:21 ` Peter Horton [this message]
2013-03-22 21:14 ` on-die ECC support David Mosberger-Tang
2013-03-23 19:27 ` Peter Horton
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
-- strict thread matches above, loose matches on Subject: below --
2013-03-15 16:08 on-die " David Mosberger-Tang
2013-03-15 16:17 ` David Mosberger-Tang
2013-03-15 17:58 ` Peter Horton
2013-03-20 17:46 ` David Mosberger-Tang
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=514C147B.3030609@bitbox.co.uk \
--to=phorton@bitbox.co.uk \
--cc=dmosberger@gmail.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 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.