OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/include/linker/common-rom.ld

96 lines
2.5 KiB
Plaintext
Raw Normal View History

interrupts: simplify position of sw ISR table We now place the linker directives for the SW ISR table in the common linker scripts, instead of repeating it everywhere. The table will be placed in RAM if dynamic interrupts are enabled. A dedicated section is used, as this data must not move in between build phases. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-11-09 06:44:31 +08:00
#if defined(CONFIG_GEN_ISR_TABLES) && !defined(CONFIG_DYNAMIC_INTERRUPTS)
SECTION_PROLOGUE(sw_isr_table, (OPTIONAL),)
{
*(SW_ISR_TABLE)
} GROUP_LINK_IN(ROMABLE_REGION)
#endif
build: consolidate some common parts of linker scripts There are a number of data sections that are repeated across all the linker scripts for various architecture. In practice these don't always get updated and we have had problems with bit-rot. Consolidate these to make maintenance easier. x86 linker scripts now follow the same naming convention and we get rid of a linker-epilog.h that wasn't necessary and whose purpose has been lost to the mists of time. If applications want to define their own sections they should be allowed to. Linker scripts for x86 do not end with .h any more, they are not C header files even though we use C's preprocessor. Issue: ZEP-688 Change-Id: I893eb4619969695c1f980efd7c2ec9fa5dad136d Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 23:09:32 +08:00
#ifdef CONFIG_CPLUSPLUS
SECTION_PROLOGUE(_CTOR_SECTION_NAME,,)
{
/*
* The compiler fills the constructor pointers table below,
* hence symbol __CTOR_LIST__ must be aligned on 4 byte
* boundary. To align with the C++ standard, the first elment
* of the array contains the number of actual constructors. The
* last element is NULL.
*/
. = ALIGN(4);
__CTOR_LIST__ = .;
LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2)
KEEP(*(SORT_BY_NAME(".ctors*")))
LONG(0)
__CTOR_END__ = .;
} GROUP_LINK_IN(ROMABLE_REGION)
SECTION_PROLOGUE(init_array, (OPTIONAL),)
{
. = ALIGN(4);
__init_array_start = .;
KEEP(*(SORT_BY_NAME(".init_array*")))
__init_array_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
#endif
userspace: add K_THREAD_ACCCESS_GRANT() It's possible to declare static threads that start up as K_USER, but these threads can't do much since they start with permissions on no kernel objects other than their own thread object. Rather than do some run-time synchronization to have some other thread grant the necessary permissions, we introduce macros to conveniently assign object permissions to these threads when they are brought up at boot by the kernel. The tables generated here are constant and live in ROM when possible. Example usage: K_THREAD_DEFINE(my_thread, STACK_SIZE, my_thread_entry, NULL, NULL, NULL, 0, K_USER, K_NO_WAIT); K_THREAD_ACCESS_GRANT(my_thread, &my_sem, &my_mutex, &my_pipe); Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-18 02:20:22 +08:00
#ifdef CONFIG_USERSPACE
/* Build-time assignment of permissions to kernel objects to
* threads declared with K_THREAD_DEFINE()
*/
SECTION_PROLOGUE(object_access, (OPTIONAL),)
{
__object_access_start = .;
KEEP(*(".object_access.*"))
__object_access_end = .;
}
#endif
build: consolidate some common parts of linker scripts There are a number of data sections that are repeated across all the linker scripts for various architecture. In practice these don't always get updated and we have had problems with bit-rot. Consolidate these to make maintenance easier. x86 linker scripts now follow the same naming convention and we get rid of a linker-epilog.h that wasn't necessary and whose purpose has been lost to the mists of time. If applications want to define their own sections they should be allowed to. Linker scripts for x86 do not end with .h any more, they are not C header files even though we use C's preprocessor. Issue: ZEP-688 Change-Id: I893eb4619969695c1f980efd7c2ec9fa5dad136d Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 23:09:32 +08:00
SECTION_PROLOGUE (devconfig, (OPTIONAL),)
{
__devconfig_start = .;
*(".devconfig.*")
KEEP(*(SORT_BY_NAME(".devconfig*")))
__devconfig_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
net: Remove unused net sections net_l2_init sections used to exist in early stage of the native IP stack but got removed since. Change-Id: I189d6e6f7aa05a6e5a62a28973c714d0367b0c5a Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-10-25 16:02:05 +08:00
SECTION_PROLOGUE(net_l2, (OPTIONAL),)
net: L2 might need private data per-interface Allocate the right amount of space for L2's context. Change-Id: Ia2f4f4162334e9e9c26dc95230abdfde5986e052 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-06-16 19:50:38 +08:00
{
__net_l2_start = .;
*(".net_l2.init")
KEEP(*(SORT_BY_NAME(".net_l2.init*")))
__net_l2_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
Bluetooth: settings: Add support for per-submodule handlers Add a new linker section for a list of submodule settings handlers, and iterate the list from the various settings callbacks. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-04-27 18:24:02 +08:00
#if defined(CONFIG_BT_SETTINGS)
SECTION_DATA_PROLOGUE(_bt_settings_area, (OPTIONAL), SUBALIGN(4))
{
_bt_settings_start = .;
KEEP(*(SORT_BY_NAME("._bt_settings.static.*")))
_bt_settings_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
#endif
logging: subsystem major redesign Adding new implementation of logging subsystem. New features includes: support for multiple backends, improving performance by deferring log processing to the known context, adding timestamps and logs filtering options (compile time, runtime, module level, instance level). Console backend added as the example backend. Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2018-05-16 14:50:33 +08:00
SECTION_DATA_PROLOGUE(log_const_sections, (OPTIONAL),)
{
__log_const_start = .;
KEEP(*(SORT(.log_const_*)));
__log_const_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
SECTION_DATA_PROLOGUE(log_backends_sections, (OPTIONAL),)
{
__log_backends_start = .;
KEEP(*(".log_backends"));
__log_backends_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
shell: Shell subsystem reimplementation New shell support features like: - multi-instance - command tree - static and dynamic commands - multiline - help print function - smart tab (autocompletion) - meta-keys - history, wildcards etc. - generic transport (initially, uart present) Signed-off-by: Jakub Rzeszutko <jakub.rzeszutko@nordicsemi.no> Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no> Signed-off-by: Piotr Zięcik <piotr.ziecik@nordicsemi.no>
2018-08-09 15:56:10 +08:00
SECTION_DATA_PROLOGUE(shell_root_cmds_sections, (OPTIONAL),)
{
__shell_root_cmds_start = .;
KEEP(*(SORT(.shell_root_cmd_*)));
__shell_root_cmds_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)
subsys: add monochrome character framebuffer Add monochrome character framebuffer for monochrome graphic dot matrix displays and electrophoretic displays. These displays are mostly monochrome and can only display black and some other color, for example white. Typically, a byte controls 8 pixels, arranged vertically or horizontally depending on the controller or settings. The API is not suitable to display graphics, the purpose is to display text or symbols. It is possible to use several fonts. A font can also consist of graphic symbols only and thus, for example, enable the realization of a menu. Signed-off-by: Johann Fischer <j.fischer@phytec.de>
2018-07-19 23:43:39 +08:00
SECTION_DATA_PROLOGUE(font_entry_sections, (OPTIONAL),)
{
__font_entry_start = .;
KEEP(*(SORT_BY_NAME(".font_entry.*")))
__font_entry_end = .;
} GROUP_LINK_IN(ROMABLE_REGION)