From: Roger Quadros <rogerq@kernel.org>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: Michael Trimarchi <michael@amarulasolutions.com>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
u-boot@lists.denx.de
Subject: Re: U-Boot OMAP GPMC ECC change
Date: Wed, 10 May 2023 12:42:43 +0300 [thread overview]
Message-ID: <1944d1d1-399d-dfde-16ae-21a00ff7fbe3@kernel.org> (raw)
In-Reply-To: <ZFpnUpyyT4h55BtC@colin-ia-desktop>
Hi Colin,
On 09/05/2023 18:31, Colin Foster wrote:
> Hi Roger,
>
> I was looking to test my system against U-Boot 2023.04. I'm running an
> OMAP 4460 SOM (I've been waiting to get kernel acceptance before U-Boot,
> but that has slipped) and it boots from NAND.
>
> When I jumped from 2023.01 to 2023.04, I noticed I get spammed in the
> SPL by "omap-elm: uncorrectable ECC errors". I bisected, and this seems
> to be the result of commit 04fcd25873 ("mtd: rawnand: omap_gpmc: Fix
> BCH6/16 HW based correction").
oops. Sorry about that.
>
> Is the multi-sector ECC generation something that should work in a
> backward-compatible way? Do you know of anything that might be going
> wrong here?
The patch wasn't supposed to break anything.
I do not yet know what could be wrong. Most likely a wrong ECC
configuration is being used.
Could you please share what ECC configuration you are using on your board?
Can you please point me to the Linux device tree file if it exists?
>
> Any advice would be greatly appreciated, as I find it is usually
> something simple I'm doing wrong that is causing most of my issues.
>
>
> Thanks,
>
> Colin Foster.
--
cheers,
-roger
next prev parent reply other threads:[~2023-05-10 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 15:31 U-Boot OMAP GPMC ECC change Colin Foster
2023-05-10 9:42 ` Roger Quadros [this message]
2023-05-10 15:38 ` Colin Foster
2023-05-12 11:53 ` Roger Quadros
2023-05-12 16:05 ` Colin Foster
2023-05-13 5:59 ` Roger Quadros
2023-05-17 13:30 ` Roger Quadros
2023-05-17 19:39 ` Colin Foster
2023-05-18 10:55 ` Roger Quadros
2023-05-18 23:19 ` Colin Foster
2023-05-19 12:41 ` Roger Quadros
2023-05-20 17:27 ` Colin Foster
2023-06-26 5:03 ` Michael Nazzareno Trimarchi
2023-06-27 5:42 ` Colin Foster
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=1944d1d1-399d-dfde-16ae-21a00ff7fbe3@kernel.org \
--to=rogerq@kernel.org \
--cc=colin.foster@in-advantage.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=michael@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox