Instead of having to enable ramfunc support manually, just make it transparently available to users, keeping the MPU region disabled if not used to not waste a MPU region. This however wastes 24 bytes of code area when the MPU is disabled and 48 bytes when it is enabled, and probably a dozen of CPU cycles during boot. I believe it is something acceptable. Note that when XIP is used, code is already in RAM, so the __ramfunc keyword does nothing, but does not generate an error. Signed-off-by: Aurelien Jarno <aurelien@aurel32.net> |
||
|---|---|---|
| .. | ||
| common-ram.ld | ||
| common-rom.ld | ||
| debug-sections.ld | ||
| intlist.ld | ||
| kobject-rom.ld | ||
| kobject-text.ld | ||
| kobject.ld | ||
| linker-defs.h | ||
| linker-tool-gcc.h | ||
| linker-tool.h | ||
| priv_stacks-noinit.ld | ||
| priv_stacks-rom.ld | ||
| priv_stacks-text.ld | ||
| priv_stacks.ld | ||
| rel-sections.ld | ||
| section_tags.h | ||
| sections.h | ||