From: Grant Likely <grant.likely@secretlab.ca>
To: linuxppc-embedded@ozlabs.org, paulus@samba.org
Cc: Peter Korsgaard <jacmet@sunsite.dk>,
Andrei Konovalov <akonovalov@ru.mvista.com>,
Rick Moleres <Rick.Moleres@xilinx.com>
Subject: [PATCH 1/7] [PPC] Rework Kconfig dependancies for Xilinx Virtex ppc405 platform
Date: Fri, 27 Apr 2007 13:49:59 -0600 [thread overview]
Message-ID: <1177703413868-git-send-email-grant.likely@secretlab.ca> (raw)
In-Reply-To: <1177703413970-git-send-email-grant.likely@secretlab.ca>
Reverse dependency order for Xilinx Virtex parts. For these parts, It
makes more sense for boards/chips to specify which features they
provide instead of the features listing the parts they are implemented
in. I think it also makes adding new board ports simpler.
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Acked-by: Peter Korsgaard <jacmet@sunsite.dk>
---
arch/ppc/platforms/4xx/Kconfig | 15 +++++++--------
1 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/arch/ppc/platforms/4xx/Kconfig b/arch/ppc/platforms/4xx/Kconfig
index 705ae56..76551b6 100644
--- a/arch/ppc/platforms/4xx/Kconfig
+++ b/arch/ppc/platforms/4xx/Kconfig
@@ -29,6 +29,7 @@ config CPCI405
config EP405
bool "EP405/EP405PC"
+ select EMBEDDEDBOOT
help
This option enables support for the EP405/EP405PC boards.
@@ -54,11 +55,15 @@ config WALNUT
config XILINX_ML300
bool "Xilinx-ML300"
+ select XILINX_VIRTEX_II_PRO
+ select EMBEDDEDBOOT
help
This option enables support for the Xilinx ML300 evaluation board.
config XILINX_ML403
bool "Xilinx-ML403"
+ select XILINX_VIRTEX_4_FX
+ select EMBEDDEDBOOT
help
This option enables support for the Xilinx ML403 evaluation board.
endchoice
@@ -215,18 +220,14 @@ config 405GPR
config XILINX_VIRTEX_II_PRO
bool
- depends on XILINX_ML300
- default y
+ select XILINX_VIRTEX
config XILINX_VIRTEX_4_FX
bool
- depends on XILINX_ML403
- default y
+ select XILINX_VIRTEX
config XILINX_VIRTEX
bool
- depends on XILINX_VIRTEX_II_PRO || XILINX_VIRTEX_4_FX
- default y
config STB03xxx
bool
@@ -235,8 +236,6 @@ config STB03xxx
config EMBEDDEDBOOT
bool
- depends on EP405 || XILINX_ML300 || XILINX_ML403
- default y
config IBM_OPENBIOS
bool
--
1.5.1
next prev parent reply other threads:[~2007-04-27 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 19:49 [PATCH 0/7] Revised Xilinx virtex establish sanity patchset Grant Likely
2007-04-27 19:49 ` Grant Likely
2007-04-27 19:49 ` Grant Likely [this message]
2007-04-27 19:50 ` [PATCH 2/7] [PPC] Merge common virtex header files Grant Likely
2007-04-27 19:50 ` [PATCH 3/7] [PPC] New registration for common Xilinx Virtex ppc405 platform devices Grant Likely
2007-04-27 19:50 ` [PATCH 4/7] [PPC] Stop using ppc_sys for Xilinx Virtex boards Grant Likely
2007-04-27 19:50 ` [PATCH 5/7] [PPC] Add uartlite boot console driver for the zImage wrapper Grant Likely
2007-04-27 19:50 ` [PATCH 6/7] [PPC] Add sane defaults for Xilinx EDK generated xparameters files Grant Likely
2007-04-27 19:50 ` [PATCH 7/7] [PPC] Don't define a custom bd_t for Xilixn Virtex based boards Grant Likely
2007-04-28 1:53 ` XILINX SPI IP core with INTC IP core Leonid
2007-04-30 15:31 ` Rick Moleres
2007-04-30 16:19 ` Leonid
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=1177703413868-git-send-email-grant.likely@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=Rick.Moleres@xilinx.com \
--cc=akonovalov@ru.mvista.com \
--cc=jacmet@sunsite.dk \
--cc=linuxppc-embedded@ozlabs.org \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).