Training courses

Kernel and Embedded Linux

Bootlin training courses

Embedded Linux, kernel,
Yocto Project, Buildroot, real-time,
graphics, boot time, debugging...

Bootlin logo

Elixir Cross Referencer

#
# Kconfig for uClinux(non-paged MM) depend configurations
# Hyok S. Choi <hyok.choi@samsung.com>
# 

config 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 CONFIG_DRAM_BASE
	hex '(S)DRAM Base Address' if CONFIG_SET_MEM_PARAM
	default 0x00800000

config CONFIG_DRAM_SIZE
	hex '(S)DRAM SIZE' if CONFIG_SET_MEM_PARAM
	default 0x00800000

config CONFIG_FLASH_MEM_BASE
	hex 'FLASH Base Address' if CONFIG_SET_MEM_PARAM
	default 0x00400000

config CONFIG_FLASH_SIZE
	hex 'FLASH Size' if CONFIG_SET_MEM_PARAM
	default 0x00400000

config CONFIG_PROCESSOR_ID
	hex 'Hard wire the processor ID'
	default 0x00007700
	depends on !(CONFIG_CPU_CP15 || CONFIG_CPU_V7M)
	help
	  If processor has no CP15 register, this processor ID is
	  used instead of the auto-probing which utilizes the register.

config CONFIG_REMAP_VECTORS_TO_RAM
	bool 'Install vectors to the beginning of RAM' if CONFIG_DRAM_BASE
	depends on CONFIG_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 CONFIG_DRAM_BASE.

config CONFIG_ARM_MPU
       bool 'Use the CONFIG_ARM v7 PMSA Compliant CONFIG_MPU'
       depends on CONFIG_CPU_V7
       default y
       help
         Some CONFIG_ARM systems without an CONFIG_MMU have instead a Memory Protection
         Unit (CONFIG_MPU) that defines the type and permissions for regions of
         memory.

         If your CPU has an CONFIG_MPU then you should choose 'y' here unless you
         know that you do not want to use the CONFIG_MPU.