zephyr/subsys/llext
Guennadi Liakhovetski dbea13a1c7 llext: fix read-only extension image
When using the LLEXT buffer loader we now avoid copying extensions
from storage to allocated memory by pointing directly into the stored
image. We then also perform linking and relocation in that memory,
which modifies its contents. However, this is impossible if that
storage is read-only. Add a Kconfig flag to distinguish between
writable and read-only storage types. Also use that flag to decide,
whether the extension image in test_llext_simple.c should be defined
as const or not.

Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
2023-12-01 10:08:12 -05:00
..
buf_loader.c llext: add llext_peek() 2023-11-10 10:40:26 +01:00
CMakeLists.txt llext: export some symbols 2023-12-01 10:08:12 -05:00
Kconfig llext: fix read-only extension image 2023-12-01 10:08:12 -05:00
llext_export.c llext: export some symbols 2023-12-01 10:08:12 -05:00
llext.c llext: fix read-only extension image 2023-12-01 10:08:12 -05:00
shell.c llext: remove llext list scanning from shell.c 2023-12-01 10:08:12 -05:00