| /trusted-firmware-a/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 …]
|
| /trusted-firmware-a/ |
| A D | .commitlintrc.js | 19 function getScopes(sections) { argument
20 return sections.flatMap(section => {
22 const subscopes = getScopes(section.sections || []);
30 const scopes = getScopes(cz.sections); /* Contains every blessed scope */
|
| A D | .versionrc.js | 41 "sections": cz.sections, property in module.exports.preset
|
| A D | Makefile | 403 -ffunction-sections -fdata-sections \
427 TF_LDFLAGS += -Wl,--gc-sections
444 TF_LDFLAGS += --gc-sections
|
| /trusted-firmware-a/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 ~}}
|
| /trusted-firmware-a/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
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | index.rst.txt | 7 In the next sections, we first give a description of the target of evaluation
|
| A D | threat_model_spm.rst.txt | 95 The following sections define:
339 | | SPMC code/data sections. |
|
| /trusted-firmware-a/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 | 95 The following sections define:
339 | | SPMC code/data sections. |
|
| /trusted-firmware-a/services/std_svc/rmmd/trp/ |
| A D | linker.lds | 9 /* Mapped using 4K pages, requires us to align different sections with
|
| /trusted-firmware-a/docs/process/ |
| A D | commit-style.rst | 112 "sections": [
115 "sections": [
119 "sections": [
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/process/ |
| A D | commit-style.rst.txt | 112 "sections": [
115 "sections": [
119 "sections": [
|
| /trusted-firmware-a/lib/romlib/ |
| A D | Makefile | 34 LDFLAGS := --gc-sections -O1
|
| /trusted-firmware-a/plat/nvidia/tegra/scat/ |
| A D | bl31.scat | 81 /* Place pubsub sections for events */
|
| /trusted-firmware-a/docs/design/ |
| A D | firmware-design.rst | 78 The sections below provide the following details:
158 path as described in the following sections.
846 The following sections describe the framework which facilitates the
917 call handling functions are provided in the following sections.
1523 sections;
1529 In the ELF terminology, they are called ``NOBITS`` sections.
1531 All PROGBITS sections are grouped together at the beginning of the image,
1539 For BL31, a platform can specify an alternate location for NOBITS sections
1540 (other than immediately following PROGBITS sections) by setting
1673 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.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | firmware-design.rst.txt | 78 The sections below provide the following details:
158 path as described in the following sections.
846 The following sections describe the framework which facilitates the
917 call handling functions are provided in the following sections.
1523 sections;
1529 In the ELF terminology, they are called ``NOBITS`` sections.
1531 All PROGBITS sections are grouped together at the beginning of the image,
1539 For BL31, a platform can specify an alternate location for NOBITS sections
1540 (other than immediately following PROGBITS sections) by setting
1673 sections must not overstep. The platform code must provide those.
[all …]
|
| A D | reset-design.rst.txt | 22 configuration, some of these steps might be unnecessary. The following sections
|
| A D | trusted-board-boot.rst.txt | 201 described in the following sections.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | ras.rst.txt | 225 As mentioned in earlier sections, RAS framework interacts with the |EHF| to
|
| /trusted-firmware-a/docs/components/ |
| A D | ras.rst | 225 As mentioned in earlier sections, RAS framework interacts with the |EHF| to
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | build-options.rst | 63 the RW sections in RAM, while leaving the RO sections in place. This option
626 sections of BL31 (.bss, stacks, page tables, and coherent memory) to be
630 sections are placed in RAM immediately following the loaded firmware image.
|