From: Ivan Djelic <ivan.djelic@parrot.com>
To: Gerlando Falauto <gerlando.falauto@keymile.com>
Cc: "Bigler, Stefan" <Stefan.Bigler@keymile.com>,
Christopher Harvey <charvey@matrox.com>,
"Brunck, Holger" <Holger.Brunck@keymile.com>,
Ricard Wanderlof <ricard.wanderlof@axis.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: state of support for "external ECC hardware"
Date: Mon, 12 Nov 2012 18:35:15 +0100 [thread overview]
Message-ID: <20121112173515.GA3041@parrot.com> (raw)
In-Reply-To: <50A12FBD.8020801@keymile.com>
On Mon, Nov 12, 2012 at 05:19:57PM +0000, Gerlando Falauto wrote:
(...)
> > At any rate, the ECC algorithm itself should be able to take care of bit
> > flips in the ECC codes. For the 1-bit algorithm in nand_ecc.c it does this
> > by comparing the computed ECC with the actual ECC; if there's a difference
> > of exactly one bit (rather than a more complex diff which after
> > calculations points out the flipped bit in the main area), it is assumed
> > that the bitflip is in the ECC area rather than the data. I don't know how
> > BCH does this though.
>
> Ivan, I came to understand (but I am not sure), that the implementation
> you provided (and currently mainlined) *DOES* handle this correctly. It
> was instead an old one which did not handle this properly. Is my
> understanding correct?
Yes you are correct. In BCH ECC, there is no difference between data and ecc bytes, they are
all part of larger codeword on which error correction is performed.
An old patch introducing BCH support in nand/omap2.c had a bug which was triggered when a bitflip
was detected in ecc bytes; but this has nothing to do with the way BCH algorithms work.
BR,
--
Ivan
next prev parent reply other threads:[~2012-11-12 17:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:42 state of support for "external ECC hardware" Christopher Harvey
2012-11-08 11:02 ` Gerlando Falauto
2012-11-08 15:21 ` Christopher Harvey
2012-11-08 16:32 ` Gerlando Falauto
2012-11-08 16:37 ` Gerlando Falauto
2012-11-08 17:03 ` Christopher Harvey
2012-11-08 17:02 ` Christopher Harvey
2012-11-08 19:07 ` Ivan Djelic
2012-11-09 8:46 ` Ricard Wanderlof
2012-11-12 17:19 ` Gerlando Falauto
2012-11-12 17:35 ` Ivan Djelic [this message]
2012-11-12 17:39 ` Gerlando Falauto
2012-11-12 18:52 ` Ivan Djelic
2012-11-14 10:12 ` Gerlando Falauto
2012-11-14 13:24 ` Angus CLARK
2012-11-14 14:48 ` Matthieu CASTET
2012-11-14 20:22 ` Ivan Djelic
2012-11-20 11:13 ` Calvin Johnson
2012-11-20 11:35 ` Gerlando Falauto
2012-11-20 12:12 ` Calvin Johnson
2012-11-20 16:16 ` Ricard Wanderlof
2012-11-08 18:59 ` Ivan Djelic
2012-11-08 19:22 ` Christopher Harvey
2012-11-08 19:33 ` Ivan Djelic
2012-11-08 18:04 ` Ivan Djelic
2012-11-14 10:59 ` Angus CLARK
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=20121112173515.GA3041@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=Holger.Brunck@keymile.com \
--cc=Stefan.Bigler@keymile.com \
--cc=charvey@matrox.com \
--cc=gerlando.falauto@keymile.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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 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.