From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Fix compile errors for atmel_nand with hw-ecc and new SoC access
Date: Fri, 2 Apr 2010 11:38:54 -0500 [thread overview]
Message-ID: <20100402163854.GA5796@loki.buserror.net> (raw)
In-Reply-To: <1269780145-6396-3-git-send-email-holler@ahsoftware.de>
On Sun, Mar 28, 2010 at 02:42:25PM +0200, Alexander Holler wrote:
> atmel_nand.c with HW-ECC doesn't compile with the new SoC access.
> Using CONFIG_AT91_LEGACY to circumvent the compile errors only leaves
> the driver in a state where it doesn't find the NAND.
>
> To use HW-ECC with atmel_nand one has to use
> CONFIG_SYS_NAND_ECC_BASE AT91_ECC0_BASE (instead of AT91_ECC0)
> for an AT91SAM9263 or AT91_ECC_BASE for an AT91SAM9260.
>
> I've removed three unused variables too.
> ---
> drivers/mtd/nand/atmel_nand.c | 7 +++----
> 1 files changed, 3 insertions(+), 4 deletions(-)
Missing Signed-off-by line.
-Scott
next prev parent reply other threads:[~2010-04-02 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 6:55 [U-Boot] [PATH] at91: add hwecc method for nand Nikolay Petukhov
2010-03-18 22:46 ` Scott Wood
2010-03-19 5:49 ` Nikolay Petukhov
2010-03-19 22:17 ` Scott Wood
2010-03-28 12:42 ` [U-Boot] [PATCH 0/2] atmel_nand with HW-ECC Alexander Holler
2010-03-28 12:42 ` [U-Boot] [PATCH 1/2] Add AT91_ECC_BASE to at91sam9260.h to use " Alexander Holler
2010-03-28 12:42 ` [U-Boot] [PATCH 2/2] Fix compile errors for atmel_nand with hw-ecc and new SoC access Alexander Holler
2010-04-02 16:38 ` Scott Wood [this message]
2010-04-03 11:08 ` Alexander Holler
2010-04-03 11:08 ` [U-Boot] [PATCH 1/2] Add AT91_ECC_BASE to at91sam9260.h to use atmel_nand with HW-ECC Alexander Holler
2010-04-03 11:08 ` [U-Boot] [PATCH 2/2] Fix compile errors for atmel_nand with hw-ecc and new SoC access Alexander Holler
2010-04-04 16:26 ` Tom
2010-04-04 17:26 ` Alexander Holler
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=20100402163854.GA5796@loki.buserror.net \
--to=scottwood@freescale.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