From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc/85xx: Simplify the top makefile for P1_P2_RDB boards
Date: Thu, 10 Sep 2009 17:07:05 -0500 [thread overview]
Message-ID: <4AA97889.5090505@freescale.com> (raw)
In-Reply-To: <1252618408-31375-3-git-send-email-galak@kernel.crashing.org>
Kumar Gala wrote:
> diff --git a/include/configs/P2020DS.h b/include/configs/P2020DS.h
> index 2a2b9ac..f987f7a 100644
> --- a/include/configs/P2020DS.h
> +++ b/include/configs/P2020DS.h
> @@ -27,6 +27,10 @@
> #ifndef __CONFIG_H
> #define __CONFIG_H
>
> +#ifdef CONFIG_MK_P2020DS_36BIT
> +#define CONFIG_PHYS_64BIT
> +#endif
> +
> /* High Level Configuration Options */
> #define CONFIG_BOOKE 1 /* BOOKE */
> #define CONFIG_E500 1 /* BOOKE e500 family */
[snip]
> diff --git a/include/configs/P1_P2_RDB.h b/include/configs/P1_P2_RDB.h
> index 6d44d6c..8e97ad0 100644
> --- a/include/configs/P1_P2_RDB.h
> +++ b/include/configs/P1_P2_RDB.h
> @@ -30,6 +30,19 @@
> #ifndef __CONFIG_H
> #define __CONFIG_H
>
> +#ifdef CONFIG_MK_P1011RDB
> +#define CONFIG_P1011
> +#endif
> +#ifdef CONFIG_MK_P1020RDB
> +#define CONFIG_P1020
> +#endif
> +#ifdef CONFIG_MK_P2010RDB
> +#define CONFIG_P2010
> +#endif
> +#ifdef CONFIG_MK_P2020RDB
> +#define CONFIG_P2020
> +#endif
I hope nobody ever wants to stick an alternate boot source (such as
NAND), board revs, 36 bit, etc. on top of this 4-way choice.
I thought Wolfgang had finally agreed to the splitting approach. :-(
-Scott
prev parent reply other threads:[~2009-09-10 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 21:33 [U-Boot] [PATCH] ppc/85xx: Simplify the top makefile for 36-bit config for MPC8572DS Kumar Gala
2009-09-10 21:33 ` [U-Boot] [PATCH] ppc/85xx: Simplify the top makefile for 36-bit config for P2020DS Kumar Gala
2009-09-10 21:33 ` [U-Boot] [PATCH] ppc/85xx: Simplify the top makefile for P1_P2_RDB boards Kumar Gala
2009-09-10 22:07 ` Scott Wood [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=4AA97889.5090505@freescale.com \
--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