diff options
| author | Greg Ungerer <gerg@uclinux.org> | 2011-10-14 00:43:30 -0400 |
|---|---|---|
| committer | Greg Ungerer <gerg@uclinux.org> | 2011-12-29 19:20:21 -0500 |
| commit | e08d703cc2ab6e47dbd10a74eb029f7dfa93d71d (patch) | |
| tree | f81a41ca2a92ed39a723b024b984d220373e6e01 /arch/m68k/Kconfig.cpu | |
| parent | 2c9b82adb5ea65745d5d73d97bb0e1cc16cba4a0 (diff) | |
m68k: modify user space access functions to support ColdFire CPUs
Modify the user space access functions to support the ColdFire V4e cores
running with MMU enabled.
The ColdFire processors do not support the "moves" instruction used by
the traditional 680x0 processors for moving data into and out of another
address space. They only support the notion of a single address space,
and you use the usual "move" instruction to access that.
Create a new config symbol (CONFIG_CPU_HAS_ADDRESS_SPACES) to mark the
CPU types that support separate address spaces, and thus also support
the sfc/dfc registers and the "moves" instruction that go along with that.
The code is almost identical for user space access, so lets just use a
define to choose either the "move" or "moves" in the assembler code.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Acked-by: Matt Waddel <mwaddel@yahoo.com>
Acked-by: Kurt Mahan <kmahan@xmission.com>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'arch/m68k/Kconfig.cpu')
| -rw-r--r-- | arch/m68k/Kconfig.cpu | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu index 017f4fc388d2..5ae1d63ef5e9 100644 --- a/arch/m68k/Kconfig.cpu +++ b/arch/m68k/Kconfig.cpu | |||
| @@ -38,6 +38,7 @@ config M68020 | |||
| 38 | bool "68020 support" | 38 | bool "68020 support" |
| 39 | depends on MMU | 39 | depends on MMU |
| 40 | select GENERIC_ATOMIC64 | 40 | select GENERIC_ATOMIC64 |
| 41 | select CPU_HAS_ADDRESS_SPACES | ||
| 41 | help | 42 | help |
| 42 | If you anticipate running this kernel on a computer with a MC68020 | 43 | If you anticipate running this kernel on a computer with a MC68020 |
| 43 | processor, say Y. Otherwise, say N. Note that the 68020 requires a | 44 | processor, say Y. Otherwise, say N. Note that the 68020 requires a |
| @@ -48,6 +49,7 @@ config M68030 | |||
| 48 | bool "68030 support" | 49 | bool "68030 support" |
| 49 | depends on MMU && !MMU_SUN3 | 50 | depends on MMU && !MMU_SUN3 |
| 50 | select GENERIC_ATOMIC64 | 51 | select GENERIC_ATOMIC64 |
| 52 | select CPU_HAS_ADDRESS_SPACES | ||
| 51 | help | 53 | help |
| 52 | If you anticipate running this kernel on a computer with a MC68030 | 54 | If you anticipate running this kernel on a computer with a MC68030 |
| 53 | processor, say Y. Otherwise, say N. Note that a MC68EC030 will not | 55 | processor, say Y. Otherwise, say N. Note that a MC68EC030 will not |
| @@ -57,6 +59,7 @@ config M68040 | |||
| 57 | bool "68040 support" | 59 | bool "68040 support" |
| 58 | depends on MMU && !MMU_SUN3 | 60 | depends on MMU && !MMU_SUN3 |
| 59 | select GENERIC_ATOMIC64 | 61 | select GENERIC_ATOMIC64 |
| 62 | select CPU_HAS_ADDRESS_SPACES | ||
| 60 | help | 63 | help |
| 61 | If you anticipate running this kernel on a computer with a MC68LC040 | 64 | If you anticipate running this kernel on a computer with a MC68LC040 |
| 62 | or MC68040 processor, say Y. Otherwise, say N. Note that an | 65 | or MC68040 processor, say Y. Otherwise, say N. Note that an |
| @@ -67,6 +70,7 @@ config M68060 | |||
| 67 | bool "68060 support" | 70 | bool "68060 support" |
| 68 | depends on MMU && !MMU_SUN3 | 71 | depends on MMU && !MMU_SUN3 |
| 69 | select GENERIC_ATOMIC64 | 72 | select GENERIC_ATOMIC64 |
| 73 | select CPU_HAS_ADDRESS_SPACES | ||
| 70 | help | 74 | help |
| 71 | If you anticipate running this kernel on a computer with a MC68060 | 75 | If you anticipate running this kernel on a computer with a MC68060 |
| 72 | processor, say Y. Otherwise, say N. | 76 | processor, say Y. Otherwise, say N. |