From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Orjan Friberg <of@flatfrog.com>
Cc: 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:56:30 +0100 [thread overview]
Message-ID: <4F547FBE.4030805@parrot.com> (raw)
In-Reply-To: <4F5475A8.3050600@flatfrog.com>
Hi,
Orjan Friberg a écrit :
> 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).
>
Note that the omap driver is still broken :
http://article.gmane.org/gmane.linux.drivers.mtd/36079/match=
We detected this when stressing a board.
Because all of these bugs in omap driver, I wonder how many people really use
the mainline version.
Also if you use a nand that need 4-bit ECC, you need a better ecc than hamming.
You can use the bch code (
http://article.gmane.org/gmane.linux.drivers.mtd/37864/match=omap )
Matthieu
PS : why omap driver use in omap_dev_ready GPMC*IRQ_STATUS instead of GPMC_STATUS.
PS2 : ecc hamming look strange. Weird isEccFF code. Doesn't seem to handle bit
flip in ecc.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-05 8:56 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
2012-03-05 8:56 ` Matthieu CASTET [this message]
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=4F547FBE.4030805@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=of@flatfrog.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).