From: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/9 V4] convert common files to new SoC access
Date: Wed, 10 Feb 2010 12:25:46 +0100 [thread overview]
Message-ID: <4B7297BA.8080001@esd.eu> (raw)
In-Reply-To: <4B69EED2.8040604@scharsoft.de>
Hello Jens,
Jens Scharsig wrote:
> * add's a warning to all files, which need update to new SoC access
> * convert common files in cpu/../at91 and a lot of drivers to use
> c stucture SoC access
>
>
> Signed-off-by: Jens Scharsig <js_at_ng@scharsoft.de>
<snip>
> diff --git a/drivers/i2c/soft_i2c.c b/drivers/i2c/soft_i2c.c
> index 9a48783..e0cf1e1 100644
> --- a/drivers/i2c/soft_i2c.c
> +++ b/drivers/i2c/soft_i2c.c
> @@ -30,14 +30,15 @@
> #include <ioports.h>
> #include <asm/io.h>
> #endif
> -#ifdef CONFIG_AT91RM9200 /* need this for the at91rm9200 */
> +#if defined(CONFIG_AT91RM9200) || \
> + defined(CONFIG_AT91SAM9260) || defined(CONFIG_AT91SAM9261) || \
> + defined(CONFIG_AT91SAM9263)
> #include <asm/io.h>
> #include <asm/arch/hardware.h>
> -#endif
> -#ifdef CONFIG_AT91SAM9263 /* only valid for AT91SAM9263 */
> -#include <asm/arch/at91_pmc.h>
Please don't remove this include. It breaks build on AT91SAM9263 boards who have
CONFIG_AT91_LEGACY enabled. (e.g. new otc570 board)
> +#include <asm/arch/at91_pio.h>
> +#ifdef CONFIG_AT91_LEGACY
> #include <asm/arch/gpio.h>
> -#include <asm/arch/io.h>
dito
> +#endif
> #endif
> #ifdef CONFIG_IXP425 /* only valid for IXP425 */
> #include <asm/arch/ixp425.h>
Best regards,
Daniel Gorsulowski
next prev parent reply other threads:[~2010-02-10 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 11:03 [U-Boot] [PATCH 5/9 V3] convert common files to new SoC access Jens Scharsig
2010-01-31 1:20 ` Tom
2010-01-31 16:15 ` Jens Scharsig
2010-02-03 21:46 ` [U-Boot] [PATCH 5/9 V4] " Jens Scharsig
2010-02-10 11:25 ` Daniel Gorsulowski [this message]
2010-02-11 7:38 ` Daniel Gorsulowski
2010-02-11 7:52 ` Daniel Gorsulowski
2010-02-11 9:11 ` Daniel Gorsulowski
2010-02-14 11:25 ` Jens Scharsig
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=4B7297BA.8080001@esd.eu \
--to=daniel.gorsulowski@esd.eu \
--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