m68k: modify user space access functions to support ColdFire CPUs
authorGreg Ungerer <gerg@uclinux.org>
Fri, 14 Oct 2011 04:43:30 +0000 (14:43 +1000)
committerGreg Ungerer <gerg@uclinux.org>
Fri, 30 Dec 2011 00:20:21 +0000 (10:20 +1000)
commite08d703cc2ab6e47dbd10a74eb029f7dfa93d71d
treef81a41ca2a92ed39a723b024b984d220373e6e01
parent2c9b82adb5ea65745d5d73d97bb0e1cc16cba4a0
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>
arch/m68k/Kconfig
arch/m68k/Kconfig.cpu
arch/m68k/include/asm/segment.h
arch/m68k/include/asm/uaccess_mm.h
arch/m68k/lib/uaccess.c