From: Orjan Friberg <of@flatfrog.com>
To: Grazvydas Ignotas <notasas@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Spurious ECC errors with mtd_subpagetest (OMAP3, NAND)
Date: Mon, 5 Mar 2012 09:13:28 +0100 [thread overview]
Message-ID: <4F5475A8.3050600@flatfrog.com> (raw)
In-Reply-To: <CANOLnOM6X=29r7_aMs=z4eiDtw0kvWZ-jSeds_NO0KdZ3E8Ouw@mail.gmail.com>
On 03/02/2012 06:17 PM, Grazvydas Ignotas wrote:
> IIRC NAND in mainline was broken for very long time on OMAP3, I think
> it was only fixed in 2.6.39.1.
That seems to be the case; the 2.6.39.1 diff contains the OMAP NAND sub
page write fix (applied locally).
Anyone else who can testify on the "volatile-ness" of NAND ECC errors?
I.e., are they expected to be more persistent?
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
next prev parent reply other threads:[~2012-03-05 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 16:17 Spurious ECC errors with mtd_subpagetest (OMAP3, NAND) Orjan Friberg
2012-03-02 16:42 ` Orjan Friberg
2012-03-02 17:17 ` Grazvydas Ignotas
2012-03-05 8:13 ` Orjan Friberg [this message]
2012-03-05 8:56 ` Matthieu CASTET
2012-03-05 9:09 ` Orjan Friberg
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=4F5475A8.3050600@flatfrog.com \
--to=of@flatfrog.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.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;
as well as URLs for NNTP newsgroup(s).