| /trusted-firmware-a-3.6.0-3.5.0/docs/getting_started/ |
| D | build-internals.rst | 5 :ref:`build-options <build options>` but enabled or disabled indirectly and
6 depends on certain options to be enabled or disabled.
12 interest when Armv8.4-SecEL2 or RME extension is implemented.
14 and ``SPMD_SPM_AT_SEL2`` is set or when ``ENABLE_RME`` is set to 1 (enabled).
|
| 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. Arm Compiler 6 will be selected
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-3.6.0-3.5.0/plat/nxp/soc-ls1043a/ |
| D | soc.def | 17 # set to GIC400 or GIC500
20 # set to CCI400 or CCN504 or CCN508
23 # indicate layerscape chassis level - set to 3=LSCH3 or 2=LSCH2
26 # TZC IP Details TZC used is TZC380 or TZC400
29 # CONSOLE Details available is NS16550 or PL011
37 # ddr controller - set to MMDC or NXP
40 # ddr phy - set to NXP or SNPS
|
| /trusted-firmware-a-3.6.0-3.5.0/plat/nxp/soc-ls1046a/ |
| D | soc.def | 17 # set to GIC400 or GIC500
20 # set to CCI400 or CCN504 or CCN508
23 # indicate layerscape chassis level - set to 3=LSCH3 or 2=LSCH2
26 # TZC IP Details TZC used is TZC380 or TZC400
29 # CONSOLE Details available is NS16550 or PL011
37 # ddr controller - set to MMDC or NXP
40 # ddr phy - set to NXP or SNPS
|
| /trusted-firmware-a-3.6.0-3.5.0/plat/nxp/soc-ls1088a/ |
| D | soc.def | 17 # Set to GIC400 or GIC500
20 # Set to CCI400 or CCN504 or CCN508
28 # Indicate layerscape chassis level - set to 3=LSCH3 or 2=LSCH2
31 # TZC IP Details TZC used is TZC380 or TZC400
34 # CONSOLE Details available is NS16550 or PL011
|
| /trusted-firmware-a-3.6.0-3.5.0/ |
| 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-3.6.0-3.5.0/plat/nxp/soc-ls1028a/ |
| 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-3.6.0-3.5.0/fdts/ |
| D | stm32mp157c-dhcom-pdk2.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-3-Clause
8 * DHCOM PCB number: 587-200 or newer
9 * PDK2 PCB number: 516-400 or newer
|
| D | stm32mp157a-dhcor-avenger96.dts | 10 * DHCOR PCB number: 586-100 or newer
11 * Avenger96 PCB number: 588-200 or newer
|
| D | stm32mp157c-dhcom-pdk2-fw-config.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-3-Clause
|
| /trusted-firmware-a-3.6.0-3.5.0/plat/nxp/soc-lx2160a/ |
| 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-3.6.0-3.5.0/docs/threat_model/ |
| D | threat_model_el3_spm.rst | 25 - Not covering advanced or invasive physical attacks such as decapsulation,
47 | DF1 | SP to SPMC communication. FF-A function invocation or |
59 | | LSP can send direct response SP1 or NWd through SPMC. |
110 NS-EL2 (Hypervisor) or NS-EL1 (VM or OS kernel).
113 such as bus probing or DRAM stress.
129 analysis is evaluated based on the environment being ``Server`` or ``Mobile``.
223 | | driver, or Hypervisor although it remains untrusted|
260 | | PARTITION_INFO_GET or memory sharing primitives. |
275 | Threat | **An endpoint may tamper with its own state or the |
280 | | - its own or another SP state by using an unusual |
[all …]
|
| 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.
44 - Not covering advanced or invasive physical attacks such as decapsulation,
46 - Assumes secure boot or in particular TF-A trusted boot (TBBR or dual CoT) is
48 SiP or platform providers.
70 | ``DF1`` | SP to SPMC communication. FF-A function invocation or |
136 (Hypervisor) or NS-EL1 (VM or OS kernel).
[all …]
|
| D | threat_model.rst | 29 - All TF-A images are run from either ROM or on-chip trusted SRAM. This means
30 TF-A is not vulnerable to an attacker that can probe or tamper with off-chip
49 there are no other assets to protect or threats to defend against that
97 | | with TF-A through SMC call interface and/or shared |
101 | | with TF-A through SMC call interface and/or shared |
137 | | of Trust Public Key) or see (e.g. secure logs, |
160 | NSCode | | Malicious or faulty code running in the Non-secure |
163 | SecCode | | Malicious or faulty code running in the secure |
178 ion beam (FIB) workstation or decapsulate the chip using chemicals) is
186 or more of these types: ``Spoofing``, ``Tampering``, ``Repudiation``,
[all …]
|
| /trusted-firmware-a-3.6.0-3.5.0/lib/compiler-rt/ |
| 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-3.6.0-3.5.0/docs/process/ |
| D | platform-ports-policy.rst | 11 documented in the :ref:`Porting Guide`), driver APIs (like the GICv3 drivers) or
23 to upstream their platform code or copy the latest version of the code being
38 If a platform, driver or library interface is no longer maintained, it is best
40 can be a 1-stage or 2-stage process (up to the maintainers).
50 platform ports (or soon to be) to this day.
|
| 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 …]
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/plat/ |
| 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
|
| D | allwinner.rst | 45 some build options that allow to fine-tune the firmware, or to disable support
50 to be loaded into the ARISC SCP (A64, H5), or the power sequence control
70 regulators, or some regulators need to be enabled in a very specific
73 entirely. Any bootloader or OS would need to setup the PMIC on its own then.
79 Loading is done from SD card, eMMC or SPI flash, also via an USB debug
84 bl31.bin can be either copied (or sym-linked) into U-Boot's root directory,
85 or the environment variable BL31 must contain the binary's path.
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/components/ |
| D | el3-spmc.rst | 46 - BL32 option is re-purposed to specify the S-EL1 TEE or SP image.
48 - BL33 option can specify the TFTF binary or a normal world loader
49 such as U-Boot or the UEFI framework payload.
90 for managing access control, programming TZ Controller or MPUs.
234 boot (that is prior to NWd is booted) or run-time.
239 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
253 When invoked from the Hypervisor or OS kernel, the buffers are mapped into the
258 caller, either it being the Hypervisor or OS kernel, as well as a secure
267 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
269 The format (v1.0 or v1.1) of the populated data structure returned is based upon the
[all …]
|
| 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-3.6.0-3.5.0/include/export/ |
| 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-3.6.0-3.5.0/docs/about/ |
| D | contact.rst | 5 it or for obtaining support.
16 enquiries, enhancement requests and issue reports, or to follow and participate
17 in technical or organizational discussions around the project. These discussions
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/security_advisories/ |
| 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
|
| /trusted-firmware-a-3.6.0-3.5.0/licenses/ |
| D | LICENSE.MIT | 8 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
13 copies or substantial portions of the Software.
|
