| /trusted-firmware-a/ |
| A D | dco.txt | 17 (a) The contribution was created in whole or in part by me and I
19 indicated in the file; or
24 work with modifications, whether created in whole or in part
27 in the file; or
30 person who certified (a), (b) or (c) and I have not modified
37 this project or the open source license(s) involved.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_downloads/64c40a63b9b2c30373557926065e7bb2/ |
| A D | dco.txt | 17 (a) The contribution was created in whole or in part by me and I
19 indicated in the file; or
24 work with modifications, whether created in whole or in part
27 in the file; or
30 person who certified (a), (b) or (c) and I have not modified
37 this project or the open source license(s) involved.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | threat_model_spm.rst.txt | 8 (SPM) implementation or more generally the S-EL2 reference firmware running on
16 - Isolation of mutually mistrusting SW components, or endpoints in the FF-A
24 or the Hypervisor).
29 In this threat model, the target of evaluation is the S-EL2 firmware or the
37 The threat model is not related to the normal world Hypervisor or VMs.
43 - Not covering advanced or invasive physical attacks such as decapsulation,
45 - Assumes secure boot or in particular TF-A trusted boot (TBBR or dual CoT) is
47 SiP or platform providers.
135 (Hypervisor) or NS-EL1 (VM or OS kernel).
138 such as bus probing or DRAM stress.
[all …]
|
| A D | threat_model.rst.txt | 27 - All TF-A images are run from either ROM or on-chip trusted SRAM. This means
28 TF-A is not vulnerable to an attacker that can probe or tamper with off-chip
66 | | with TF-A through SMC call interface and/or shared |
70 | | with TF-A through SMC call interface and/or shared |
104 | | of Trust Public Key) or see (e.g. secure logs, |
126 | ``NSCode`` | | Malicious or faulty code running in the Non-secure |
129 | ``SecCode`` | | Malicious or faulty code running in the secure |
144 ion beam (FIB) workstation or decapsulate the chip using chemicals) is
151 or more of these types: ``Spoofing``, ``Tampering``, ``Repudiation``,
152 ``Information disclosure``, ``Denial of service`` or
[all …]
|
| /trusted-firmware-a/docs/threat_model/ |
| A D | threat_model_spm.rst | 8 (SPM) implementation or more generally the S-EL2 reference firmware running on
16 - Isolation of mutually mistrusting SW components, or endpoints in the FF-A
24 or the Hypervisor).
29 In this threat model, the target of evaluation is the S-EL2 firmware or the
37 The threat model is not related to the normal world Hypervisor or VMs.
43 - Not covering advanced or invasive physical attacks such as decapsulation,
45 - Assumes secure boot or in particular TF-A trusted boot (TBBR or dual CoT) is
47 SiP or platform providers.
135 (Hypervisor) or NS-EL1 (VM or OS kernel).
138 such as bus probing or DRAM stress.
[all …]
|
| A D | threat_model.rst | 27 - All TF-A images are run from either ROM or on-chip trusted SRAM. This means
28 TF-A is not vulnerable to an attacker that can probe or tamper with off-chip
66 | | with TF-A through SMC call interface and/or shared |
70 | | with TF-A through SMC call interface and/or shared |
104 | | of Trust Public Key) or see (e.g. secure logs, |
126 | ``NSCode`` | | Malicious or faulty code running in the Non-secure |
129 | ``SecCode`` | | Malicious or faulty code running in the secure |
144 ion beam (FIB) workstation or decapsulate the chip using chemicals) is
151 or more of these types: ``Spoofing``, ``Tampering``, ``Repudiation``,
152 ``Information disclosure``, ``Denial of service`` or
[all …]
|
| /trusted-firmware-a/plat/nxp/soc-ls1028a/ |
| A D | soc.def | 17 # Set to GIC400 or GIC500
20 # Set to CCI400 or CCN504 or CCN508
23 # Layerscape chassis level - set to 3=LSCH3 or 2=LSCH2
26 # TZC used is TZC380 or TZC400
29 # CONSOLE is NS16550 or PL011
|
| /trusted-firmware-a/plat/nxp/soc-lx2160a/ |
| A D | soc.def | 18 # set to GIC400 or GIC500
21 # set to CCI400 or CCN504 or CCN508
24 # indicate layerscape chassis level - set to 3=LSCH3 or 2=LSCH2
27 # TZC IP Details TZC used is TZC380 or TZC400
30 # CONSOLE Details available is NS16550 or PL011
|
| /trusted-firmware-a/lib/compiler-rt/ |
| A D | LICENSE.TXT | 32 use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
41 documentation and/or other materials provided with the distribution.
45 endorse or promote products derived from this Software without specific
63 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
68 all copies or substantial portions of the Software.
88 other licenses gives permission to use the names of the LLVM Team or the
89 University of Illinois to endorse or promote products derived from this
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | sphinxlatexindbibtoc.sty | 8 % - environments: (backup defaults or get redefined)
10 % - sphinxtheindex (direct mark-up or via python.ist or sphinx.xdy)
|
| A D | sphinxlatextables.sty | 61 % The following is to ensure that, whether tabular(y) or longtable:
95 % B. Table with tabular or tabulary
106 % move back vertically, as tabular (or its caption) will compensate
150 % or a tabulary
235 \else % either not tabulary or tabulary's second pass
242 \else % either not tabulary or tabulary's second pass
282 % trick to recognize L, C, R, J or p, m, b type columns
301 % empty space whether or not the columns were | separated:
331 % width when cells are merged either via multirow or multicolumn or both,
357 \linewidth % in a L, R, C, J column or a p, \X, \Y ...
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | debugfs-design.rst.txt | 12 TFTF test payload or a Linux kernel module.
28 - / is used as root for virtual "files" (e.g. /fip, or /dev/uart)
43 relative or an absolute offset.
68 options. The interface multiplexes drivers or emulated "files":
75 non-secure layers, or for which no support exists in the NS side).
82 shared buffer is used to pass path string parameters, or e.g. to exchange
114 - a test payload, bootloader or hypervisor running at NS-EL2
|
| /trusted-firmware-a/docs/components/ |
| A D | debugfs-design.rst | 12 TFTF test payload or a Linux kernel module.
28 - / is used as root for virtual "files" (e.g. /fip, or /dev/uart)
43 relative or an absolute offset.
68 options. The interface multiplexes drivers or emulated "files":
75 non-secure layers, or for which no support exists in the NS side).
82 shared buffer is used to pass path string parameters, or e.g. to exchange
114 - a test payload, bootloader or hypervisor running at NS-EL2
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | allwinner.rst.txt | 11 To build for machines with an A64 or H5 SoC:
23 To build for machines with an H616 or H313 SoC:
34 Loading is done from SD card, eMMC or SPI flash, also via an USB debug
39 bl31.bin can be either copied (or sym-linked) into U-Boot's root directory,
40 or the environment variable BL31 must contain the binary's path.
|
| A D | rockchip.rst.txt | 26 - U-Boot - either separately as TPL+SPL or only SPL
32 Rockchip SoCs expect TF-A's BL31 (AARCH64) or BL32 (AARCH32) to get
33 integrated with other boot software like U-Boot or Coreboot, so only
|
| /trusted-firmware-a/docs/plat/ |
| A D | allwinner.rst | 11 To build for machines with an A64 or H5 SoC:
23 To build for machines with an H616 or H313 SoC:
34 Loading is done from SD card, eMMC or SPI flash, also via an USB debug
39 bl31.bin can be either copied (or sym-linked) into U-Boot's root directory,
40 or the environment variable BL31 must contain the binary's path.
|
| A D | rockchip.rst | 26 - U-Boot - either separately as TPL+SPL or only SPL
32 Rockchip SoCs expect TF-A's BL31 (AARCH64) or BL32 (AARCH32) to get
33 integrated with other boot software like U-Boot or Coreboot, so only
|
| /trusted-firmware-a/docs/process/ |
| A D | code-review-guidelines.rst | 23 unfairly criticizing or belittling the work of any contributor.
59 - Ping the reviewers on Gerrit or on the mailing list. If it is urgent,
80 There are no good or bad review comments. If you have any doubt about a patch or
102 - It complies with the relevant standards or technical documentation (where
129 concerns, questions, or any other type of blocking comment, they should set
175 - The patch aims at complying with any standard or technical documentation
180 should help catch files with incorrect or no copyright/license headers.
182 - There is no third party code or binary blobs with potential IP concerns.
183 Maintainers should look for copyright or license notices in code, and use
201 posted via the commit message or on the mailing list.
[all …]
|
| A D | commit-style.rst | 61 | ``build`` | Changes that affect the build system or external dependencies |
76 | ``test`` | Adding missing tests or correcting existing tests |
83 file are organized by their changelog section, each of which may have one or
89 can, or add their own if no appropriate one exists (see :ref:`Adding Scopes`).
100 Scopes that are either a) unblessed in the configuration file, or b) do not
105 For example, if you are adding or making modifications to `Foo`'s latest and
150 or clone the repository using the "`Clone with commit-msg hook`" clone method,
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/process/ |
| A D | code-review-guidelines.rst.txt | 23 unfairly criticizing or belittling the work of any contributor.
59 - Ping the reviewers on Gerrit or on the mailing list. If it is urgent,
80 There are no good or bad review comments. If you have any doubt about a patch or
102 - It complies with the relevant standards or technical documentation (where
129 concerns, questions, or any other type of blocking comment, they should set
175 - The patch aims at complying with any standard or technical documentation
180 should help catch files with incorrect or no copyright/license headers.
182 - There is no third party code or binary blobs with potential IP concerns.
183 Maintainers should look for copyright or license notices in code, and use
201 posted via the commit message or on the mailing list.
[all …]
|
| A D | commit-style.rst.txt | 61 | ``build`` | Changes that affect the build system or external dependencies |
76 | ``test`` | Adding missing tests or correcting existing tests |
83 file are organized by their changelog section, each of which may have one or
89 can, or add their own if no appropriate one exists (see :ref:`Adding Scopes`).
100 Scopes that are either a) unblessed in the configuration file, or b) do not
105 For example, if you are adding or making modifications to `Foo`'s latest and
150 or clone the repository using the "`Clone with commit-msg hook`" clone method,
|
| /trusted-firmware-a/include/export/ |
| A D | README | 3 or interfaces. They must follow these special rules:
7 - All definitions should be sufficiently namespaced (e.g. with BL_ or TF_) to
20 pre-defined by all common compilers (e.g. __ASSEMBLER__ or __aarch64__).
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | docs-build.rst | 22 - Python 3 (3.5 or later)
23 - PlantUML (1.2017.15 or later)
26 existing ``.dia`` diagram files, or create new ones.
50 as root or using ``sudo``.
85 There may be cases where you can not either install or upgrade required
|
| A D | initial-build.rst | 19 It is possible to build TF-A using Clang or Arm Compiler 6. To do so
20 ``CC`` needs to point to the clang or armclang binary, which will
21 also select the clang or armclang assembler. Be aware that for Arm Compiler,
99 is either ``debug`` or ``release``. The actual number of images might differ
108 ... where ``<D>`` is ``0`` or ``1``, as specified when building.
|
| /trusted-firmware-a/docs/security_advisories/ |
| A D | security-advisory-tfv-3.rst | 14 | Configurations | AArch64 BL2, TSP or other users of xlat_tables library |
36 the client specified ``MT_EXECUTE`` or ``MT_EXECUTE_NEVER``.
42 unexpectedly executable instead of non-executable. Other platforms or
53 Note that one or more separate vulnerabilities are also required to exploit this
68 of the ``XN``, ``UXN`` or ``PXN`` bits in the translation tables. See the
|