summaryrefslogtreecommitdiffstats
path: root/arch/m68k
diff options
context:
space:
mode:
authorLuis Alves <ljalvs@gmail.com>2012-10-25 21:01:16 +0100
committerGreg Ungerer <gerg@uclinux.org>2012-12-05 10:51:20 +1000
commit9da1a84a9125dab0c95f045068e36512334ab473 (patch)
tree0ccda941c1a2e667a7ebfca84096e15886c854d6 /arch/m68k
parent4674e8d385c34498a329fc31b41f449dc419014d (diff)
downloadop-kernel-dev-9da1a84a9125dab0c95f045068e36512334ab473.zip
op-kernel-dev-9da1a84a9125dab0c95f045068e36512334ab473.tar.gz
m68knommu: disable MC68000 cpu target when MMU is selected
As pointed out by Geert, MC68000 target needs to be disabled when MMU support is enabled. From Geert: This needs a "depends on !MMU". Else allmodconfig will select it, causing -m68000 to be passed to the assembler, which may break the build depending on your version of binutils, a.o. arch/m68k/kernel/entry.S:186: Error: invalid instruction for this architecture; needs 68020 or higher (68020 [68k, 68ec020], 68030 [68ec030], 68040 [68ec040], 68060 [68ec060]) -- statement `bfextu %sp@(50){#0,#4},%d0' ignored arch/m68k/kernel/entry.S:211: Error: invalid operand mode for this architecture; needs 68020 or higher -- statement `jbsr @(sys_call_table,%d0:l:4)@(0)' ignored Cfr. http://kisskb.ellerman.id.au/kisskb/buildresult/7416877/ Signed-off-by: Luis Alves <ljalvs@gmail.com> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Diffstat (limited to 'arch/m68k')
-rw-r--r--arch/m68k/Kconfig.cpu1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
index aad3b0b..6708fa4 100644
--- a/arch/m68k/Kconfig.cpu
+++ b/arch/m68k/Kconfig.cpu
@@ -36,6 +36,7 @@ if M68KCLASSIC
config M68000
bool "MC68000"
+ depends on !MMU
select CPU_HAS_NO_BITFIELDS
select CPU_HAS_NO_MULDIV64
select CPU_HAS_NO_UNALIGNED
OpenPOWER on IntegriCloud