mirror of
https://github.com/torvalds/linux.git
synced 2024-12-23 19:31:53 +00:00
216218308c
Currently, there is assumption in early MPU setup code that kernel image is located in RAM, which is obviously not true for XIP. To run code from ROM we need to make sure that it is covered by MPU. However, due to we allocate regions (semi-)dynamically we can run into issue of trimming region we are running from in case ROM spawns several MPU regions. To help deal with that we enforce minimum alignments for start end end of XIP address space as 1MB and 128Kb correspondingly. Tested-by: Alexandre TORGUE <alexandre.torgue@st.com> Tested-by: Benjamin Gaignard <benjamin.gaignard@linaro.org> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
64 lines
1.9 KiB
Plaintext
64 lines
1.9 KiB
Plaintext
#
|
|
# Kconfig for uClinux(non-paged MM) depend configurations
|
|
# Hyok S. Choi <hyok.choi@samsung.com>
|
|
#
|
|
|
|
config SET_MEM_PARAM
|
|
bool "Set flash/sdram size and base addr"
|
|
help
|
|
Say Y to manually set the base addresses and sizes.
|
|
otherwise, the default values are assigned.
|
|
|
|
config DRAM_BASE
|
|
hex '(S)DRAM Base Address' if SET_MEM_PARAM
|
|
default 0x00800000
|
|
|
|
config DRAM_SIZE
|
|
hex '(S)DRAM SIZE' if SET_MEM_PARAM
|
|
default 0x00800000
|
|
|
|
config FLASH_MEM_BASE
|
|
hex 'FLASH Base Address' if SET_MEM_PARAM
|
|
default 0x00400000
|
|
|
|
config FLASH_SIZE
|
|
hex 'FLASH Size' if SET_MEM_PARAM
|
|
default 0x00400000
|
|
|
|
config PROCESSOR_ID
|
|
hex 'Hard wire the processor ID'
|
|
default 0x00007700
|
|
depends on !(CPU_CP15 || CPU_V7M)
|
|
help
|
|
If processor has no CP15 register, this processor ID is
|
|
used instead of the auto-probing which utilizes the register.
|
|
|
|
config REMAP_VECTORS_TO_RAM
|
|
bool 'Install vectors to the beginning of RAM'
|
|
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.
|
|
|
|
config ARM_MPU
|
|
bool 'Use the ARM v7 PMSA Compliant MPU'
|
|
depends on CPU_V7 || CPU_V7M
|
|
default y if CPU_V7
|
|
help
|
|
Some ARM systems without an MMU have instead a Memory Protection
|
|
Unit (MPU) that defines the type and permissions for regions of
|
|
memory.
|
|
|
|
If your CPU has an MPU then you should choose 'y' here unless you
|
|
know that you do not want to use the MPU.
|