summaryrefslogtreecommitdiff
path: root/arch/arm/Kconfig-nommu
diff options
context:
space:
mode:
authorHyok S. Choi <hyok.choi@samsung.com>2006-03-27 18:18:50 +0400
committerRussell King <rmk+kernel@arm.linux.org.uk>2006-03-27 18:18:50 +0400
commitc760fc1997e8156ebc4134c42c18f68137c689f9 (patch)
treed7ab9b7b93c8d6829a7d2b6d972b8405256d04d0 /arch/arm/Kconfig-nommu
parentf8c07de6beac55c3273cbd679bfa67555ef14ef5 (diff)
downloadlinux-c760fc1997e8156ebc4134c42c18f68137c689f9.tar.xz
[ARM] nommu: fixups for the exception vectors
The high page vector (0xFFFF0000) does not supported in nommu mode. This patch allows the vectors to be 0x00000000 or the begining of DRAM in nommu mode. Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/Kconfig-nommu')
-rw-r--r--arch/arm/Kconfig-nommu17
1 files changed, 17 insertions, 0 deletions
diff --git a/arch/arm/Kconfig-nommu b/arch/arm/Kconfig-nommu
index 8ce56e5bd78f..e1574be2ded6 100644
--- a/arch/arm/Kconfig-nommu
+++ b/arch/arm/Kconfig-nommu
@@ -25,3 +25,20 @@ config FLASH_SIZE
hex 'FLASH Size' if SET_MEM_PARAM
default 0x00400000
+config REMAP_VECTORS_TO_RAM
+ bool 'Install vectors to the begining of RAM' if DRAM_BASE
+ depends on DRAM_BASE
+ help
+ The kernel needs to change the hardware exception vectors.
+ In nommu mode, the hardware exception vectors are normally
+ placed at address 0x00000000. However, this region may be
+ occupied by read-only memory depending on H/W design.
+
+ If the region contains read-write memory, say 'n' here.
+
+ If your CPU provides a remap facility which allows the exception
+ vectors to be mapped to writable memory, say 'n' here.
+
+ Otherwise, say 'y' here. In this case, the kernel will require
+ external support to redirect the hardware exception vectors to
+ the writable versions located at DRAM_BASE.