mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-06 22:07:12 +00:00
Some platforms may have multiple RAM regions which are dis-continuous in the physical memory map. We really want these to be in a continuous virtual region, and we need to stop assuming that there is just one SRAM region that is identity-mapped. We no longer use CONFIG_SRAM_BASE_ADDRESS and CONFIG_SRAM_SIZE as the bounds of kernel RAM, and no longer assume in the core kernel that these are identity mapped at boot. Two new Kconfigs, CONFIG_KERNEL_VM_BASE and CONFIG_KERNEL_RAM_SIZE now indicate the bounds of this region in virtual memory. We are currently only memory-mapping physical device driver MMIO regions so we do not need virtual-to-physical calculations to re-map RAM yet. When the time comes an architecture interface will be defined for this. Platforms which just have one RAM region may continue to identity-map it. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> |
||
---|---|---|
.. | ||
include | ||
atomic_c.c | ||
cache_handlers.c | ||
CMakeLists.txt | ||
compiler_stack_protect.c | ||
device.c | ||
errno.c | ||
fatal.c | ||
futex.c | ||
idle.c | ||
init.c | ||
Kconfig | ||
kheap.c | ||
mailbox.c | ||
mem_domain.c | ||
mem_slab.c | ||
mempool_sys.c | ||
mempool.c | ||
mmu.c | ||
msg_q.c | ||
mutex.c | ||
pipes.c | ||
poll.c | ||
queue.c | ||
sched.c | ||
sem.c | ||
smp.c | ||
stack.c | ||
system_work_q.c | ||
thread_abort.c | ||
thread.c | ||
timeout.c | ||
timer.c | ||
userspace_handler.c | ||
userspace.c | ||
version.c | ||
work_q.c |