public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Erickson <marathon96@gmail.com>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Grazvydas Ignotas <notasas@gmail.com>,
	"Ghorai, Sukumar" <s-ghorai@ti.com>
Subject: Re: No more software ECC in omap2.c NAND driver. Why?
Date: Sun, 21 Nov 2010 22:08:52 -0800	[thread overview]
Message-ID: <C90F48F4.2031A%marathon96@gmail.com> (raw)
In-Reply-To: <201011221001.22909.manningc2@actrix.gen.nz>

On 11/21/10 1:01 PM, Charles Manning wrote:
> Just recompiling with the CONFIG_MTD_NAND_OMAP_HWECC define commented out did
> not result in a working system. I suspect there is more tto the problem than
> this.

FWIW, I had the exact same issues with my Mistral AM37x EVM board. I not
only had to remove/deassert CONFIG_MTD_NAND_OMAP_HWECC, but also had to roll
back nand_base.c and nand_bbt.c back to their 2.6.32 versions (later ones
between .32 and .35 might have worked but I didn't bother trying) to be able
to read, error-free and correctly, NAND that was erased and written with a
.32-era kernel.

Best,

Grant Erickson



  reply	other threads:[~2010-11-22  6:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  1:06 No more software ECC in omap2.c NAND driver. Why? Charles Manning
2010-11-18 14:33 ` Ghorai, Sukumar
2010-11-19 10:35   ` Grazvydas Ignotas
2010-11-19 20:45     ` Ghorai, Sukumar
2010-11-21 21:01   ` Charles Manning
2010-11-22  6:08     ` Grant Erickson [this message]
2010-11-22  6:27       ` Ghorai, Sukumar
2010-11-22  6:39         ` Grant Erickson
2010-11-22  7:29           ` Ghorai, Sukumar
2010-11-22 19:03             ` Grant Erickson
2010-11-24 14:08               ` Ghorai, Sukumar

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=C90F48F4.2031A%marathon96@gmail.com \
    --to=marathon96@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=notasas@gmail.com \
    --cc=s-ghorai@ti.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