From: Lucas Stach <dev@lynxeye.de>
To: barebox@lists.infradead.org
Subject: [PATCH 6/8] tegra: don't force to choose between Tegra arches
Date: Sun, 29 Sep 2013 21:59:34 +0200 [thread overview]
Message-ID: <1380484776-32266-7-git-send-email-dev@lynxeye.de> (raw)
In-Reply-To: <1380484776-32266-1-git-send-email-dev@lynxeye.de>
There is nothing technically preventing a single Tegra 20/30
image to be built. Don't force this split in Kconfig.
Signed-off-by: Lucas Stach <dev@lynxeye.de>
---
arch/arm/mach-tegra/Kconfig | 19 ++++++-------------
1 file changed, 6 insertions(+), 13 deletions(-)
diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig
index 4164f56..90c0c0f 100644
--- a/arch/arm/mach-tegra/Kconfig
+++ b/arch/arm/mach-tegra/Kconfig
@@ -5,15 +5,6 @@ config ARCH_TEXT_BASE
default 0x0
choice
- prompt "Tegra processor type"
-
-config ARCH_TEGRA_2x_SOC
- bool "Tegra 20"
- select PINCTRL_TEGRA20
-
-endchoice
-
-choice
prompt "Tegra debug UART"
help
This is the first serial console that gets activated by barebox.
@@ -48,18 +39,22 @@ endchoice
# ---------------------------------------------------------
-if ARCH_TEGRA_2x_SOC
+config ARCH_TEGRA_2x_SOC
+ bool
+ select PINCTRL_TEGRA20
choice
- prompt "Tegra 20 Board Type"
+ prompt "select Tegra Board"
config MACH_TEGRA20_GENERIC
bool "Generic DT based board"
+ select ARCH_TEGRA_2x_SOC
help
Say Y here if you are building for a generic DT based board.
config MACH_TOSHIBA_AC100
bool "Toshiba AC100"
+ select ARCH_TEGRA_2x_SOC
help
Say Y here if you are using Toshiba AC100 smartbook.
@@ -71,8 +66,6 @@ endif #MACH_TEGRA20_GENERIC
source arch/arm/boards/toshiba-ac100/Kconfig
-endif #ARCH_TEGRA_2x_SOC
-
# ---------------------------------------------------------
endif
--
1.8.3.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-09-29 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 19:59 [PATCH 0/8] Tegra multi image support Lucas Stach
2013-09-29 19:59 ` [PATCH 1/8] images: correctly linebreak built images output Lucas Stach
2013-10-02 8:20 ` Sascha Hauer
2013-09-29 19:59 ` [PATCH 2/8] tegra: try harder inlining early startup functions Lucas Stach
2013-09-29 19:59 ` [PATCH 3/8] tegra: start maincomplex execution at correct offset Lucas Stach
2013-09-29 19:59 ` [PATCH 4/8] tegra: fix PBL build Lucas Stach
2013-09-29 19:59 ` [PATCH 5/8] tegra: mandate relocatable binary Lucas Stach
2013-09-29 19:59 ` Lucas Stach [this message]
2013-09-29 19:59 ` [PATCH 7/8] tegra: ac100: delete custom Kconfig Lucas Stach
2013-09-29 19:59 ` [PATCH 8/8] tegra: switch to multi image Lucas Stach
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=1380484776-32266-7-git-send-email-dev@lynxeye.de \
--to=dev@lynxeye.de \
--cc=barebox@lists.infradead.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