From: Gary Thomas <gary@mlbassoc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND ECC mixup?
Date: Fri, 16 Apr 2010 09:55:19 -0600 [thread overview]
Message-ID: <4BC88867.1090004@mlbassoc.com> (raw)
I'm having trouble with NAND ECC on my OMAP/3530 platform. It
seems that U-Boot and Linux don't agree on the ECC patterns for
a given set of data.
In particular, if I create the U-Boot environment in NAND, then
update it via fw_setconfig in Linux, U-Boot is no longer happy
with the ECC bits.
I noticed that the file drivers/mtd/nand/nand_ecc.c has changed
dramatically in the Linux sources. Could this be the problem?
My code is based on git://git.denx.de/u-boot.git
15fba3279b56333bdb65ead366f82c945ed320d1 ppc/85xx: Disable all async interrupt sources when we boot
My Linux kernel is 2.6.31 or newer
I looked in the latest tree and didn't see anything relevant.
Am I missing something?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2010-04-16 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 15:55 Gary Thomas [this message]
2010-04-16 17:39 ` [U-Boot] NAND ECC mixup? Gary Thomas
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=4BC88867.1090004@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=u-boot@lists.denx.de \
/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.