| /arm-trusted-firmware-2.8.0/tools/conventional-changelog-tf-a/ |
| A D | index.js | 56 const flattenSections = function (sections) { argument
57 return sections.flatMap(section => {
64 const flattenedSections = flattenSections(config.sections);
71 const generateTemplateData = function (sections, notes) { argument
72 return (sections || []).flatMap(section => {
75 sections: generateTemplateData(section.sections, notes),
93 sections: generateTemplateData(config.sections, noteGroup.notes),
105 const generateTemplateData = function (sections, commits) { argument
106 return (sections || []).flatMap(section => {
109 sections: generateTemplateData(section.sections, commits),
[all …]
|
| /arm-trusted-firmware-2.8.0/ |
| A D | .versionrc.js | 37 function getTypes(sections) { argument
38 return sections.map(section => {
59 const types = getTypes(changelog.sections);
60 const sections = getSections(changelog.subsections);
71 "sections": sections, property in module.exports.preset
|
| A D | .commitlintrc.js | 34 function getTypes(sections) { argument
35 return sections.map(section => section.type)
47 const types = getTypes(changelog.sections).sort(); /* Sort alphabetically */
|
| A D | changelog.yaml | 8 # The following block describes the top-level sections of the changelog. Commits are categorized
9 # into these top-level sections based on the commit message "type":
15 sections:
70 # The following block describes the sub-sections of the changelog. These sub-sections may appear in
71 # any of the top-level sections, and describe the individual components that a change may relate to.
73 # Sub-sections have an optional associated commit message "scope":
|
| A D | Makefile | 403 -ffunction-sections -fdata-sections \
429 TF_LDFLAGS += -Wl,--gc-sections
446 TF_LDFLAGS += --gc-sections
|
| /arm-trusted-firmware-2.8.0/tools/conventional-changelog-tf-a/templates/ |
| A D | note-section.hbs | 9 {{#if sections.length ~}}
10 {{#each sections ~}}
|
| A D | commit-section.hbs | 11 {{#if sections.length ~}}
12 {{#each sections ~}}
|
| /arm-trusted-firmware-2.8.0/plat/rockchip/rk3399/drivers/m0/ |
| A D | Makefile | 37 CFLAGS := -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common
39 LDFLAGS := -Wl,--gc-sections -Wl,--build-id=none
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | index.rst | 7 In the next sections, we first give a description of the target of evaluation
|
| A D | threat_model_spm.rst | 96 The following sections define:
338 | | SPMC code/data sections. |
|
| A D | threat_model_el3_spm.rst | 74 The following sections define:
|
| /arm-trusted-firmware-2.8.0/services/std_svc/rmmd/trp/ |
| A D | linker.lds | 9 /* Mapped using 4K pages, requires us to align different sections with
|
| /arm-trusted-firmware-2.8.0/lib/romlib/ |
| A D | Makefile | 34 LDFLAGS := --gc-sections -O1
|
| /arm-trusted-firmware-2.8.0/plat/nvidia/tegra/scat/ |
| A D | bl31.scat | 81 /* Place pubsub sections for events */
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | firmware-design.rst | 78 The sections below provide the following details:
161 path as described in the following sections.
849 The following sections describe the framework which facilitates the
920 call handling functions are provided in the following sections.
1527 sections;
1533 In the ELF terminology, they are called ``NOBITS`` sections.
1535 All PROGBITS sections are grouped together at the beginning of the image,
1543 For BL31, a platform can specify an alternate location for NOBITS sections
1544 (other than immediately following PROGBITS sections) by setting
1677 sections must not overstep. The platform code must provide those.
[all …]
|
| A D | reset-design.rst | 22 configuration, some of these steps might be unnecessary. The following sections
|
| A D | trusted-board-boot.rst | 201 described in the following sections.
|
| A D | cpu-specific-build-macros.rst | 116 sections.
124 <= r0p4. This workaround can lead the linker to emit ``*.stub`` sections
|
| A D | interrupt-framework-design.rst | 83 following sub-sections describe all the possible routing models and specify
88 sub-sections is explained below.
217 #. Interrupt management: the following sections describe how interrupts are
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | build-options.rst | 63 the RW sections in RAM, while leaving the RO sections in place. This option
789 sections of BL31 (.bss, stacks, page tables, and coherent memory) to be
793 sections are placed in RAM immediately following the loaded firmware image.
796 NOLOAD sections of BL2 (.bss, stacks, page tables) to be allocated in RAM
799 flag is disabled by default and NOLOAD sections are placed in RAM immediately
|
| A D | rt-svc-writers-guide.rst | 125 the following sections.
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | ras.rst | 226 As mentioned in earlier sections, RAS framework interacts with the |EHF| to
|
| A D | rmm-el3-comms-spec.rst | 17 The below sections discuss these interfaces more in detail.
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | coding-style.rst | 4 The following sections outline the |TF-A| coding style for *C* code. The style
|
| A D | contributing.rst | 174 new files under your platform, they are covered under the following two sections:
|