All of lore.kernel.org
 help / color / mirror / Atom feed
From: Orjan Friberg <of@flatfrog.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Grazvydas Ignotas <notasas@gmail.com>
Subject: Re: Spurious ECC errors with mtd_subpagetest (OMAP3, NAND)
Date: Mon, 5 Mar 2012 10:09:44 +0100	[thread overview]
Message-ID: <4F5482D8.4040901@flatfrog.com> (raw)
In-Reply-To: <4F547FBE.4030805@parrot.com>

On 03/05/2012 09:56 AM, Matthieu CASTET wrote:
> 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.

Do you know any repo where this is working correctly (linux-omap, or one 
of the vendor trees etc)?

> 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 )

Yes, I've been looking at the BCH 4-bit code (both generic 
implementations and the OMAP GPMC-enabled one) in u-boot and linux.


-- 
Orjan Friberg
FlatFrog Laboratories AB

WARNING: multiple messages have this Message-ID (diff)
From: Orjan Friberg <of@flatfrog.com>
To: Matthieu CASTET <matthieu.castet@parrot.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 10:09:44 +0100	[thread overview]
Message-ID: <4F5482D8.4040901@flatfrog.com> (raw)
In-Reply-To: <4F547FBE.4030805@parrot.com>

On 03/05/2012 09:56 AM, Matthieu CASTET wrote:
> 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.

Do you know any repo where this is working correctly (linux-omap, or one 
of the vendor trees etc)?

> 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 )

Yes, I've been looking at the BCH 4-bit code (both generic 
implementations and the OMAP GPMC-enabled one) in u-boot and linux.


-- 
Orjan Friberg
FlatFrog Laboratories AB

  reply	other threads:[~2012-03-05  9:09 UTC|newest]

Thread overview: 10+ 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:17 ` Orjan Friberg
2012-03-02 16:42 ` Orjan Friberg
2012-03-02 17:17 ` Grazvydas Ignotas
2012-03-02 17:17   ` Grazvydas Ignotas
2012-03-05  8:13   ` Orjan Friberg
2012-03-05  8:56     ` Matthieu CASTET
2012-03-05  8:56       ` Matthieu CASTET
2012-03-05  9:09       ` Orjan Friberg [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=4F5482D8.4040901@flatfrog.com \
    --to=of@flatfrog.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matthieu.castet@parrot.com \
    --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 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.