Fwd: [PATCH] mtd: nand: Add support for Micron on-die ECC controller (rev2).
David Mosberger
davidm at egauge.net
Tue Apr 1 08:10:41 PDT 2014
[Forward as plain text. Thanks, Gmail...]
---------- Forwarded message ----------
From: David Mosberger <davidm at egauge.net>
Date: Tue, Apr 1, 2014 at 9:09 AM
Subject: Re: [PATCH] mtd: nand: Add support for Micron on-die ECC
controller (rev2).
To: Brian Norris <computersforpeace at gmail.com>
Cc: "Gupta, Pekon" <pekon at ti.com>, "dedekind1 at gmail.com"
<dedekind1 at gmail.com>, "linux-mtd at lists.infradead.org"
<linux-mtd at lists.infradead.org>, Gerhard Sittig <gsi at denx.de>
On Tue, Apr 1, 2014 at 2:36 AM, Brian Norris
<computersforpeace at gmail.com> wrote:
>
>
> But for this case, the max_bitflips count is used for determining when
> the error rate is unacceptably high, not just to see whether your data
> is currently corrupt. So if extra bitflips in this (otherwise
> unimportant) spare area might eventually cause the ECC hardware to
> report an error, then we need to count them.
>
To do this properly would require describing which OOB bytes are
included in the ECC.
I don't think that's possible with the current nand_ecclayout, no?
Also, effectively what my patch does is to make those OOB bytes not
ECC protected, which
is perfectly fine semantics as far as Linux is concerned. So yes,
what you say would be
an improvement, but it's not strictly needed.
--david
--
eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768
--
eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768
More information about the linux-mtd
mailing list