82f11bf099
If a particular project needs to add additional data to the binary image, in most cases the entire linker script needs to forked into the project space, causing maintenance issues if the main linker script is changed. Now we add some Kconfig options to allow a project to specify some additional linker scripts which get included by the main one in a few key areas: 1) In the definition to the 'rodata' section, which can allow additional data to be included in this ROM section. 2) In the definition to the 'datas' section, which allows additional data to be included in this RAM section. 3) Arbitrary additional sections to be included at the end of the binary. For 1 and 2, this is useful to include data generated outside of the normal C compilation, such as data structures that are created by special build tools. 3 is useful for including arbitrary binary blobs inside the final image, such as for peripheral or co-processor firmware. Change-Id: I5738d3d6da25f5bc96cda8ae806bf1a3fb34bd5d Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> |
||
|---|---|---|
| .. | ||
| debug | ||
| generated | ||
| Kconfig | ||
| Makefile | ||
| cpp_ctors.c | ||
| cpp_dtors.c | ||
| cpp_init_array.c | ||
| cpp_virtual.c | ||
| cpp_vtable.cpp | ||
| printk.c | ||
| reboot.c | ||
| ring_buffer.c | ||
| sys_log.c | ||