CONFIG_REMAP_VECTORS_TO_RAM: Install vectors to the beginning of RAM

General informations

The Linux kernel configuration item CONFIG_REMAP_VECTORS_TO_RAM has multiple definitions:

Install vectors to the beginning of RAM found in arch/arm/Kconfig-nommu

The configuration item CONFIG_REMAP_VECTORS_TO_RAM:

• prompt: Install vectors to the beginning of RAM
• type: bool
• depends on: (none)
• defined in arch/arm/Kconfig-nommu
• found in Linux kernels: 2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12

Help text

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.

Install vectors to the begining of RAM found in arch/arm/Kconfig-nommu

The configuration item CONFIG_REMAP_VECTORS_TO_RAM:

• prompt: Install vectors to the begining of RAM
• type: bool
• depends on: ( CONFIG_DRAM_BASE ) && ( CONFIG_DRAM_BASE )
• defined in arch/arm/Kconfig-nommu
• found in Linux kernels: 2.6.17–2.6.38

Help text

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.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: