From: Greg Ungerer <gerg@uclinux.org>
To: linux-m68k@vger.kernel.org
Cc: Greg Ungerer <gerg@uclinux.org>
Subject: [PATCH 03/10] m68knommu: make ColdFire SoC selection a choice
Date: Tue, 7 Jul 2015 16:55:17 +1000 [thread overview]
Message-ID: <1436252124-23051-4-git-send-email-gerg@uclinux.org> (raw)
In-Reply-To: <1436252124-23051-1-git-send-email-gerg@uclinux.org>
It would be nice if we could support multiple ColdFire SoC types in a
single binary - but currently the code simply does not support it.
Change the SoC selection config options to be a choice instead of
individual selectable entries.
This fixes problems with building allnoconfig, and means that a sane
linux kernel is generated for a single ColdFire SoC type.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
---
arch/m68k/Kconfig.cpu | 27 ++++++++++++++++++---------
1 file changed, 18 insertions(+), 9 deletions(-)
diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
index 62f590e..c496d48 100644
--- a/arch/m68k/Kconfig.cpu
+++ b/arch/m68k/Kconfig.cpu
@@ -125,6 +125,13 @@ endif # M68KCLASSIC
if COLDFIRE
+choice
+ prompt "ColdFire SoC type"
+ default M520x
+ help
+ Select the type of ColdFire System-on-Chip (SoC) that you want
+ to build for.
+
config M5206
bool "MCF5206"
depends on !MMU
@@ -174,9 +181,6 @@ config M525x
help
Freescale (Motorola) Coldfire 5251/5253 processor support.
-config M527x
- bool
-
config M5271
bool "MCF5271"
depends on !MMU
@@ -223,9 +227,6 @@ config M5307
help
Motorola ColdFire 5307 processor support.
-config M53xx
- bool
-
config M532x
bool "MCF532x"
depends on !MMU
@@ -251,9 +252,6 @@ config M5407
help
Motorola ColdFire 5407 processor support.
-config M54xx
- bool
-
config M547x
bool "MCF547x"
select M54xx
@@ -280,6 +278,17 @@ config M5441x
help
Freescale Coldfire 54410/54415/54416/54417/54418 processor support.
+endchoice
+
+config M527x
+ bool
+
+config M53xx
+ bool
+
+config M54xx
+ bool
+
endif # COLDFIRE
--
1.9.1
next prev parent reply other threads:[~2015-07-07 6:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 6:55 [PATCH 00/10] m68knommu: fix allnoconfig Greg Ungerer
2015-07-07 6:55 ` [PATCH 01/10] m68knommu: force setting of CONFIG_CLOCK_FREQ for ColdFire Greg Ungerer
2015-07-07 6:55 ` [PATCH 02/10] m68knommu: improve the clock configuration defaults Greg Ungerer
2015-07-07 6:55 ` Greg Ungerer [this message]
2015-07-07 6:55 ` [PATCH 04/10] m68knommu: update defconfig for m5208evb Greg Ungerer
2015-07-07 6:55 ` [PATCH 05/10] m68knommu: update defconfig for ColdFire m5249evb Greg Ungerer
2015-07-07 6:55 ` [PATCH 06/10] m68knommu: update defconfig for ColdFire m5272c3 Greg Ungerer
2015-07-07 6:55 ` [PATCH 07/10] m68knommu: update defconfig for ColdFire m5275evb Greg Ungerer
2015-07-07 6:55 ` [PATCH 08/10] m68knommu: update defconfig for ColdFire m5307c3 Greg Ungerer
2015-07-07 6:55 ` [PATCH 09/10] m68knommu: update defconfig for ColdFire m5407c3 Greg Ungerer
2015-07-07 6:55 ` [PATCH 10/10] m68knommu: update defconfig for ColdFire m5475evb Greg Ungerer
2015-07-07 9:00 ` [PATCH 00/10] m68knommu: fix allnoconfig Geert Uytterhoeven
2015-07-07 12:22 ` Greg Ungerer
2015-07-07 12:45 ` Geert Uytterhoeven
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=1436252124-23051-4-git-send-email-gerg@uclinux.org \
--to=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.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).