Searched refs:NOBITS (Results 1 – 8 of 8) sorted by relevance
| /trusted-firmware-a/bl31/ |
| A D | bl31.ld.S | 18 NOBITS (rw!a): ORIGIN = BL31_NOBITS_BASE, LENGTH = BL31_NOBITS_LIMIT - BL31_NOBITS_BASE
20 #define NOBITS RAM macro
142 STACK_SECTION >NOBITS
143 BSS_SECTION >NOBITS
144 XLAT_TABLE_SECTION >NOBITS
170 } >NOBITS
|
| /trusted-firmware-a/docs/design/ |
| A D | firmware-design.rst | 1529 In the ELF terminology, they are called ``NOBITS`` sections.
1532 followed by all NOBITS sections. This is true for all TF-A images and it is
1534 as small as possible. If a NOBITS section was inserted in between PROGBITS
1536 this NOBITS section, making the image unnecessarily bigger. Smaller images
1539 For BL31, a platform can specify an alternate location for NOBITS sections
1710 is loaded at the top of the Trusted SRAM, such that its NOBITS sections will
1769 |----------| <<<<<<<<<<<<< | BL31 NOBITS |
1807 |--------------| <<<<<<<<<<<<< | BL31 NOBITS |
1841 |----------| <<<<<<<<<<<<< | BL31 NOBITS |
1873 |----------| <<<<<<<<<<<<< | BL31 NOBITS |
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | firmware-design.rst.txt | 1529 In the ELF terminology, they are called ``NOBITS`` sections.
1532 followed by all NOBITS sections. This is true for all TF-A images and it is
1534 as small as possible. If a NOBITS section was inserted in between PROGBITS
1536 this NOBITS section, making the image unnecessarily bigger. Smaller images
1539 For BL31, a platform can specify an alternate location for NOBITS sections
1710 is loaded at the top of the Trusted SRAM, such that its NOBITS sections will
1769 |----------| <<<<<<<<<<<<< | BL31 NOBITS |
1807 |--------------| <<<<<<<<<<<<< | BL31 NOBITS |
1841 |----------| <<<<<<<<<<<<< | BL31 NOBITS |
1873 |----------| <<<<<<<<<<<<< | BL31 NOBITS |
[all …]
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | build-options.rst | 625 - ``SEPARATE_NOBITS_REGION``: Setting this option to ``1`` allows the NOBITS
629 ``BL31_NOBITS_LIMIT``. When the option is ``0`` (the default), NOBITS
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | build-options.rst.txt | 625 - ``SEPARATE_NOBITS_REGION``: Setting this option to ``1`` allows the NOBITS
629 ``BL31_NOBITS_LIMIT``. When the option is ``0`` (the default), NOBITS
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/ |
| A D | change-log.md.txt | 2182 NOBITS region to SRAM A1, convert AXP803 regulator setup code into a driver,
4258 BL3-1/BL3-2 NOBITS sections on top of them has been added to the Juno port.
4326 overlaying the BL3-1/BL3-2 NOBITS sections on top of these at runtime.
|
| /trusted-firmware-a/docs/ |
| A D | change-log.md | 2182 NOBITS region to SRAM A1, convert AXP803 regulator setup code into a driver,
4258 BL3-1/BL3-2 NOBITS sections on top of them has been added to the Juno port.
4326 overlaying the BL3-1/BL3-2 NOBITS sections on top of these at runtime.
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | trustedfirmware-a.tex | 4593 …SEPARATE\_NOBITS\_REGION}}: Setting this option to \sphinxcode{\sphinxupquote{1}} allows the NOBITS
4597 …uote{BL31\_NOBITS\_LIMIT}}. When the option is \sphinxcode{\sphinxupquote{0}} (the default), NOBITS
29239 In the ELF terminology, they are called \sphinxcode{\sphinxupquote{NOBITS}} sections.
29245 followed by all NOBITS sections. This is true for all TF\sphinxhyphen{}A images and it is
29247 as small as possible. If a NOBITS section was inserted in between PROGBITS
29249 this NOBITS section, making the image unnecessarily bigger. Smaller images
29253 For BL31, a platform can specify an alternate location for NOBITS sections
29543 is loaded at the top of the Trusted SRAM, such that its NOBITS sections will
58924 NOBITS region to SRAM A1, convert AXP803 regulator setup code into a driver,
63735 BL3\sphinxhyphen{}1/BL3\sphinxhyphen{}2 NOBITS sections on top of them has been added to the Juno p…
[all …]
|
Completed in 110 milliseconds