From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] [V2] AT91: Makes AT91SAM9261(9G10) SoC build correctly against u-boot-atmel/master
Date: Tue, 14 Jun 2011 14:53:28 +0200 [thread overview]
Message-ID: <4DF759C8.7070906@emk-elektronik.de> (raw)
In-Reply-To: <1307778621-25549-1-git-send-email-hong.xu@atmel.com>
Dear Hong Xu,
> Rework for AT91SAM9261(9G10) SoC, makes it build again.
> Based on the work for AT91SAM9260-EK.
>
> Signed-off-by: Hong Xu <hong.xu@atmel.com>
> ---
> arch/arm/cpu/arm926ejs/at91/at91sam9261_devices.c | 45 +++++-------
> arch/arm/include/asm/arch-at91/at91_spi.h | 2 +-
> arch/arm/include/asm/arch-at91/at91sam9261.h | 1 +
> .../arm/include/asm/arch-at91/at91sam9261_matrix.h | 77 +++++++++-----------
> 4 files changed, 56 insertions(+), 69 deletions(-)
>
> diff --git a/arch/arm/include/asm/arch-at91/at91_spi.h b/arch/arm/include/asm/arch-at91/at91_spi.h
> index c520e89..afe724d 100644
> --- a/arch/arm/include/asm/arch-at91/at91_spi.h
> +++ b/arch/arm/include/asm/arch-at91/at91_spi.h
> @@ -33,7 +33,7 @@ typedef struct at91_spi {
> at91_pdc_t pdc;
> } at91_spi_t;
>
> -#ifdef CONFIG_AT91_LEGACY
> +#ifdef CONFIG_ATMEL_LEGACY
This was already fixed by another patch. But the endif statement was not...
>
> #define AT91_SPI_CR 0x00 /* Control Register */
> #define AT91_SPI_SPIEN (1 << 0) /* SPI Enable */
After fixing at91_spi.h applied to u-boot-atmel/master
Best Regards,
Reinhard
prev parent reply other threads:[~2011-06-14 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 7:50 [U-Boot] [PATCH 1/2] [V2] AT91: Makes AT91SAM9261(9G10) SoC build correctly against u-boot-atmel/master Hong Xu
2011-06-11 7:50 ` [U-Boot] [PATCH 2/2] [V2] AT91: Makes AT91SAM9261(9G10)-EK " Hong Xu
2011-06-14 15:44 ` Reinhard Meyer
2011-06-14 12:53 ` Reinhard Meyer [this message]
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=4DF759C8.7070906@emk-elektronik.de \
--to=u-boot@emk-elektronik.de \
--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.