Lines Matching refs:sections
76 The sections below provide the following details:
110 as described in the following sections.
436 BL3-1 zero-init sections (e.g. `.bss`) should not contain valid data on entry,
579 The following sections describe the framework which facilitates the
654 call handling functions are provided in the following sections.
1111 sections;
1116 corresponding sections need to be allocated and initialized at run-time.
1117 In the ELF terminology, they are called `NOBITS` sections.
1119 All PROGBITS sections are grouped together at the beginning of the image,
1120 followed by all NOBITS sections. This is true for all Trusted Firmware images
1123 PROGBITS sections then the resulting binary file would contain a bunch of zero
1253 sections must not overstep. The platform code must provide those.
1269 sections will overwrite BL1 R/W data.
1280 When BL3-2 is loaded into Trusted SRAM, its NOBITS sections are allowed to
1381 sections will overwrite BL1 R/W data. This implies that BL1 global variables
1393 Trusted SRAM, its NOBITS sections are allowed to overlap BL2.
1574 The below sections analyze the data structures allocated in the coherent memory
1743 stages mentioned in the previous sections. The code is also divided into the