From: Yannick GICQUEL <yannick.gicquel@open.eurogiciel.org>
To: linux-m68k@vger.kernel.org
Subject: [RFC 1/8] m68k: coldfire: unlink FPU presence from MMU activation
Date: Wed, 8 Jul 2015 11:51:25 +0200 [thread overview]
Message-ID: <1436349092-2214-2-git-send-email-yannick.gicquel@gmail.com> (raw)
In-Reply-To: <1436349092-2214-1-git-send-email-yannick.gicquel@gmail.com>
m5441x coldfire chips contains a MMU and no FPU.
This patch allow building this chip with MMU activated.
Signed-off-by: Yannick GICQUEL <yannick.gicquel@gmail.com>
---
arch/m68k/Kconfig | 2 +-
arch/m68k/Kconfig.cpu | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
index 2dd8f63..d704c16 100644
--- a/arch/m68k/Kconfig
+++ b/arch/m68k/Kconfig
@@ -14,7 +14,7 @@ config M68K
select GENERIC_IOMAP
select GENERIC_STRNCPY_FROM_USER if MMU
select GENERIC_STRNLEN_USER if MMU
- select FPU if MMU
+ select FPU if MMU && !COLDFIRE
select ARCH_WANT_IPC_PARSE_VERSION
select ARCH_USES_GETTIMEOFFSET if MMU && !COLDFIRE
select HAVE_FUTEX_CMPXCHG if MMU && FUTEX
diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
index 33013df..3661eb4 100644
--- a/arch/m68k/Kconfig.cpu
+++ b/arch/m68k/Kconfig.cpu
@@ -257,6 +257,7 @@ config M54xx
config M547x
bool "MCF547x"
select M54xx
+ select FPU
select MMU_COLDFIRE if MMU
select HAVE_CACHE_CB
select HAVE_MBAR
@@ -265,6 +266,7 @@ config M547x
config M548x
bool "MCF548x"
+ select FPU
select MMU_COLDFIRE if MMU
select M54xx
select HAVE_CACHE_CB
@@ -274,7 +276,7 @@ config M548x
config M5441x
bool "MCF5441x"
- depends on !MMU
+ select MMU_COLDFIRE if MMU
select GENERIC_CLOCKEVENTS
select HAVE_CACHE_CB
help
--
1.9.1.286.g5172cb3
next prev parent reply other threads:[~2015-07-08 9:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:51 [RFC 0/8] m5441x: mmu support patchset Yannick GICQUEL
2015-07-08 9:51 ` Yannick GICQUEL [this message]
2015-07-08 13:36 ` [RFC 1/8] m68k: coldfire: unlink FPU presence from MMU activation Greg Ungerer
2015-07-17 10:46 ` Yannick GICQUEL
2015-07-08 14:03 ` Geert Uytterhoeven
2015-07-08 14:12 ` Greg Ungerer
2015-07-08 14:20 ` Geert Uytterhoeven
2015-07-08 9:51 ` [RFC 2/8] m68k: fix build issue in setup_arch() when no FPU Yannick GICQUEL
2015-07-08 14:04 ` Geert Uytterhoeven
2015-07-08 9:51 ` [RFC 3/8] m68k: add dummy dump_fpu() when FPU is not present Yannick GICQUEL
2015-07-08 9:51 ` [RFC 4/8] m68k: m5441x: add ColdFire 5441x CPU MMU memory init code Yannick GICQUEL
2015-07-08 13:45 ` Greg Ungerer
2015-07-08 9:51 ` [RFC 5/8] m68k: m5441x: fix ACR0 base address when MBAR is not present Yannick GICQUEL
2015-07-08 9:51 ` [RFC 6/8] m68k: m5441x: set rambar to end of SRAM physical addr space Yannick GICQUEL
2015-07-08 13:53 ` Greg Ungerer
2015-07-17 10:47 ` Yannick GICQUEL
2015-07-08 9:51 ` [RFC 7/8] m68k: mmu: add u-boot command line support in setup_arch() Yannick GICQUEL
2015-07-08 14:03 ` Greg Ungerer
2015-07-08 9:51 ` [RFC 8/8] m68k: uImage generation support Yannick GICQUEL
2015-07-08 14:07 ` [RFC 0/8] m5441x: mmu support patchset Greg Ungerer
2015-07-17 10:30 ` Yannick GICQUEL
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=1436349092-2214-2-git-send-email-yannick.gicquel@gmail.com \
--to=yannick.gicquel@open.eurogiciel.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).