Searched refs:NOBITS (Results 1 – 5 of 5) sorted by relevance
| /rk3399_ARM-atf/bl31/ |
| H A D | bl31.ld.S | 19 NOBITS (rw!a): ORIGIN = BL31_NOBITS_BASE, LENGTH = BL31_NOBITS_LIMIT - BL31_NOBITS_BASE 21 # define NOBITS RAM macro 202 STACK_SECTION >NOBITS 203 BSS_SECTION >NOBITS 204 PER_CPU >NOBITS 205 XLAT_TABLE_SECTION >NOBITS 234 } >NOBITS
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | numa-per-cpu.rst | 30 \`.stack\`, \`.bss\`, and \`xlat\` form the \`NOBITS\` sections at
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | firmware-design.rst | 1658 In the ELF terminology, they are called ``NOBITS`` sections. 1661 followed by all NOBITS sections. This is true for all TF-A images and it is 1663 as small as possible. If a NOBITS section was inserted in between PROGBITS 1665 this NOBITS section, making the image unnecessarily bigger. Smaller images 1668 For BL31, a platform can specify an alternate location for NOBITS sections 1841 is loaded at the top of the Trusted SRAM, such that its NOBITS sections will 1912 |----------| <<<<<<<<<<<<< | BL31 NOBITS | 1957 |--------------| <<<<<<<<<<<<< | BL31 NOBITS | 2002 |----------| <<<<<<<<<<<<< | BL31 NOBITS | 2048 |----------| <<<<<<<<<<<<< | BL31 NOBITS | [all …]
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-options.rst | 1019 - ``SEPARATE_NOBITS_REGION``: Setting this option to ``1`` allows the NOBITS 1023 ``BL31_NOBITS_LIMIT``. When the option is ``0`` (the default), NOBITS
|
| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 10809 NOBITS region to SRAM A1, convert AXP803 regulator setup code into a driver, 12885 BL3-1/BL3-2 NOBITS sections on top of them has been added to the Juno port. 12953 overlaying the BL3-1/BL3-2 NOBITS sections on top of these at runtime.
|