Home
last modified time | relevance | path

Searched refs:model (Results 1 – 25 of 47) sorted by relevance

12

/trusted-firmware-a-3.4.0/plat/rpi/rpi3/
Drpi3_bl1_setup.c72 const char __unused *model, __unused *info; in bl1_platform_setup() local
76 model = "Raspberry Pi 3 Model B"; in bl1_platform_setup()
80 model = "Raspberry Pi 3 Model B"; in bl1_platform_setup()
84 model = "Raspberry Pi 3 Model B+"; in bl1_platform_setup()
88 model = "Unknown"; in bl1_platform_setup()
94 NOTICE("rpi3: Detected: %s %s [0x%08x]\n", model, info, rev); in bl1_platform_setup()
/trusted-firmware-a-3.4.0/docs/threat_model/
Dthreat_model_fvp_r.rst7 This document provides a threat model for TF-A fvp_r platform.
12 In this threat model, the target of evaluation is the fvp_r platform of Trusted
17 threat-model document, :ref:`Generic Threat Model`
21 The most fundamental difference between the threat model for the current fvp_r
22 implementation compared to the general TF-A threat model, is that fvp_r is
23 currently limited to BL1 only. Any threats from the general TF-A threat model
27 system. The threat model for that runtime system, being partner-defined, is
28 out-of-scope for this threat-model.
61 threat-model document, :ref:`Generic Threat Model`
Dthreat_model_spm.rst7 This document provides a threat model for the TF-A `Secure Partition Manager`_
29 In this threat model, the target of evaluation is the S-EL2 firmware or the
31 The monitor and SPMD at EL3 are covered by the `Generic TF-A threat model`_.
33 The scope for this threat model is:
37 The threat model is not related to the normal world Hypervisor or VMs.
95 This threat model follows a similar methodology to the `Generic TF-A threat model`_.
113 .. figure:: ../resources/diagrams/spm-threat-model-trust-boundaries.png
144 The following threat categories as exposed in the `Generic TF-A threat model`_
154 Similarly this threat model re-uses the same threat risk ratings. The risk
293 | | model). The TF-A SPMC will be hardened in future |
[all …]
Dthreat_model.rst8 This document provides a generic threat model for TF-A firmware.
12 This threat model doesn't consider Root and Realm worlds introduced by
19 In this threat model, the target of evaluation is the Trusted
25 TF-A can be configured in various ways. In this threat model we consider
49 shows a model of the different components of a TF-A-based system and
131 in scope of this threat model.
154 In this threat model an advanced physical attacker that has the capability
162 In this threat model we categorize threats using the `STRIDE threat
248 In this threat model we consider three target environments:
260 rely on the platform code to implement some bits of it. This threat model aims
[all …]
/trusted-firmware-a-3.4.0/plat/allwinner/common/
Dsunxi_bl31_setup.c143 const char *model; in bl31_platform_setup() local
146 model = fdt_getprop(fdt, 0, "model", &length); in bl31_platform_setup()
148 model ?: "unknown"); in bl31_platform_setup()
/trusted-firmware-a-3.4.0/docs/design/
Dinterrupt-framework-design.rst57 Routing model
69 A routing model for a type of interrupt (generated as FIQ or IRQ) is defined as
73 routed to EL3. A routing model is applicable only when execution is not in EL3.
75 The default routing model for an interrupt type is to route it to the FEL in
99 secure state. This is a valid routing model as secure software is in
103 state. This is a valid routing model as secure software in EL3 can
107 non-secure state. This is an invalid routing model as a secure interrupt
112 non-secure state. This is a valid routing model as secure software in EL3
121 non-secure software through EL3. This is a valid routing model as secure
126 state. This is a valid routing model as secure software in EL3 can save
[all …]
/trusted-firmware-a-3.4.0/fdts/
Dstm32mp157a-dk1.dts15 model = "STMicroelectronics STM32MP157A-DK1 Discovery Board";
Dcorstone700_fpga.dts12 model = "corstone700-fpga";
Dstm32mp157c-dk2.dts16 model = "STMicroelectronics STM32MP157C-DK2 Discovery Board";
Dcorstone700_fvp.dts12 model = "corstone700-fvp";
Dstm32mp157c-odyssey.dts13 model = "Seeed Studio Odyssey-STM32MP157C Board";
Dstm32mp157c-dhcom-pdk2.dts19 model = "DH electronics STM32MP157C DHCOM Premium Developer Kit (2)";
Dstm32mp157c-ev1.dts11 model = "STMicroelectronics STM32MP157C eval daughter on eval mother";
Dfvp-ve-Cortex-A7x1.dts10 model = "V2F-1XV7 Cortex-A7x1 SMM";
Dstm32mp157c-lxa-mc1.dts16 model = "Linux Automation MC-1 board";
Dn1sdp-single-chip.dts11 model = "Arm Neoverse N1 System Development Platform";
Darm_fpga.dts16 model = "ARM FPGA";
Dfvp-foundation-gicv2-psci.dts23 model = "FVP Foundation";
Dfvp-foundation-gicv3-psci.dts23 model = "FVP Foundation";
Dfvp-ve-Cortex-A5x1.dts10 model = "V2P-CA5s";
/trusted-firmware-a-3.4.0/plat/arm/board/fvp/fdts/
Doptee_sp_manifest.dts30 run-time-model = <1>; /* SP pre-emptible. */
/trusted-firmware-a-3.4.0/docs/plat/arm/fvp/
Dindex.rst8 documentation for a detailed description of the model parameter options.
98 Since FVP model Version 11.0 Build 11.0.34 and Version 8.5 Build 0.8.5202
177 Therefore, one must modify the way the model is normally invoked in order to
188 using the following model parameters:
195 To provide the model with the EL3 payload image, the following methods may be
199 flash memory. On Base Cortex and AEM FVPs, the following model parameter
218 model parameters:
398 and enable the GICv3 device in the model. Note that without this option,
463 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
481 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to
[all …]
/trusted-firmware-a-3.4.0/docs/
Dindex.rst36 Armv8-A model and hardware platforms.
74 **Platform Ports** provides a list of the supported hardware and software-model
/trusted-firmware-a-3.4.0/include/drivers/
Draw_nand.h110 uint8_t model[20]; member
/trusted-firmware-a-3.4.0/docs/plat/
Dxilinx-zynqmp.rst56 The following power domain tree represents the power domain model used by TF-A

12