From: Yannick GICQUEL <yannick.gicquel@open.eurogiciel.org>
To: linux-m68k@vger.kernel.org
Subject: [RFC 2/8] m68k: fix build issue in setup_arch() when no FPU
Date: Wed, 8 Jul 2015 11:51:26 +0200 [thread overview]
Message-ID: <1436349092-2214-3-git-send-email-yannick.gicquel@gmail.com> (raw)
In-Reply-To: <1436349092-2214-1-git-send-email-yannick.gicquel@gmail.com>
When MMU is activated, assembler generates an illegal
instruction on target without FPU.
Related code under FPU flag condition.
Signed-off-by: Yannick GICQUEL <yannick.gicquel@gmail.com>
---
arch/m68k/kernel/setup_mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/m68k/kernel/setup_mm.c b/arch/m68k/kernel/setup_mm.c
index 5b8ec4d..0bc6f77 100644
--- a/arch/m68k/kernel/setup_mm.c
+++ b/arch/m68k/kernel/setup_mm.c
@@ -245,7 +245,7 @@ void __init setup_arch(char **cmdline_p)
* We should really do our own FPU check at startup.
* [what do we do with buggy 68LC040s? if we have problems
* with them, we should add a test to check_bugs() below] */
-#ifndef CONFIG_M68KFPU_EMU_ONLY
+#if !defined(CONFIG_M68KFPU_EMU_ONLY) && defined(CONFIG_FPU)
/* clear the fpu if we have one */
if (m68k_fputype & (FPU_68881|FPU_68882|FPU_68040|FPU_68060|FPU_COLDFIRE)) {
volatile int zero = 0;
--
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 ` [RFC 1/8] m68k: coldfire: unlink FPU presence from MMU activation Yannick GICQUEL
2015-07-08 13:36 ` 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 ` Yannick GICQUEL [this message]
2015-07-08 14:04 ` [RFC 2/8] m68k: fix build issue in setup_arch() when no FPU 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-3-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).