| /rk3399_ARM-atf/plat/rpi/rpi3/ |
| H A D | rpi3_bl1_setup.c | 83 const char __unused *model, __unused *info; in bl1_platform_setup() local 87 model = "Raspberry Pi 3 Model B"; in bl1_platform_setup() 91 model = "Raspberry Pi 3 Model B"; in bl1_platform_setup() 95 model = "Raspberry Pi 3 Model B+"; in bl1_platform_setup() 99 model = "Unknown"; in bl1_platform_setup() 105 NOTICE("rpi3: Detected: %s %s [0x%08x]\n", model, info, rev); in bl1_platform_setup()
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 5 platform's needs, providing a holistic threat model covering all of its features 7 documents which, together, form the project's threat model. These are 12 As the TF-A codebase evolves and new features get added, these threat model 18 Although our aim is eventually to provide threat model material for all 41 …: https://docs.microsoft.com/en-us/azure/security/develop/threat-modeling-tool-threats#stride-model
|
| H A D | threat_model_rse_interface.rst | 7 This document is an extension for the general TF-A threat-model. It considers 14 The scope of this threat model only includes the interface between the RSE and 16 the AP core. The threat model for the RSE firmware will be provided by the RSE 25 is the same as in the general TF-A threat-model document. 44 threat-model document, :ref:`Generic Threat Model`. All the threats listed there
|
| H A D | threat_model_arm_cca.rst | 7 This document provides a threat model of TF-A firmware for platforms with Arm 18 In this threat model, the target of evaluation is the Trusted Firmware for 31 recommended by `Arm CCA security model`_: 40 These are requirements of the `Arm CCA security model`_: 48 Note that this threat model hardens *[R0149]* requirement by forbidding to 56 This is a requirement of the `Arm CCA security model`_: 68 These are requirements of the `Arm CCA security model`_: 84 model of the different components of a TF-A-based system and their interactions 120 In this threat model, we use the same method to analyse threats as in the 129 identified in this threat model will only be given a risk rating for this [all …]
|
| H A D | threat_model_fw_update_and_recovery.rst | 7 This document provides a threat model of TF-A firmware for platforms with 14 threat model. 19 In this threat model, the target of evaluation is the Trusted Firmware for 36 of this threat model. Only additional details are pointed out. 73 attacks on it, if this is a concern in the platform's threat model. 85 of this threat model. Only additional details are pointed out.
|
| H A D | threat_model_firmware_handoff.rst | 7 This document provides a threat model of TF-A firmware for platforms that make 38 From a system perspective, we re-use the :ref:`Generic TF-A threat model 42 used (e.g., ``DF4``, and ``DF5`` in the generic model). 62 model <threat_analysis>`, adopting the STRIDE framework to categorize and assess
|
| H A D | threat_model_el3_spm.rst | 7 This document provides a threat model for the TF-A :ref:`EL3 Secure Partition Manager` 14 In this threat model, the target of evaluation is the ``Secure Partition Manager Core`` 16 The monitor and SPMD at EL3 are covered by the :ref:`Generic TF-A threat model 19 The scope for this threat model is: 74 This threat model follows a similar methodology to the :ref:`Generic TF-A threat model 119 The following threat categories as exposed in the :ref:`Generic TF-A threat model 130 Similarly this threat model re-uses the same threat risk ratings. The risk 316 | | state transitions (run-time model). | 441 | | run time model, do input validation. |
|
| /rk3399_ARM-atf/plat/allwinner/common/ |
| H A D | sunxi_bl31_setup.c | 142 const char *model; in bl31_platform_setup() local 145 model = fdt_getprop(fdt, 0, "model", &length); in bl31_platform_setup() 147 model ?: "unknown"); in bl31_platform_setup()
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 57 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 …]
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | index.rst | 11 Please also refer to the TF-A CI scripts under the `model/`_ directory for an 31 .. _model/: https://git.trustedfirmware.org/ci/tf-a-ci-scripts.git/tree/model
|
| H A D | fvp-cortex-a32.rst | 7 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to 25 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to
|
| H A D | fvp-cortex-a57-a53.rst | 7 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to 25 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
|
| /rk3399_ARM-atf/fdts/ |
| H A D | stm32mp157a-dk1.dts | 15 model = "STMicroelectronics STM32MP157A-DK1 Discovery Board";
|
| H A D | corstone700_fpga.dts | 12 model = "corstone700-fpga";
|
| H A D | stm32mp157c-dk2.dts | 16 model = "STMicroelectronics STM32MP157C-DK2 Discovery Board";
|
| H A D | corstone700_fvp.dts | 12 model = "corstone700-fvp";
|
| H A D | stm32mp157c-odyssey.dts | 13 model = "Seeed Studio Odyssey-STM32MP157C Board";
|
| H A D | stm32mp157a-dhcor-avenger96.dts | 21 model = "Arrow Electronics STM32MP157A Avenger96 board";
|
| H A D | stm32mp157c-dhcom-pdk2.dts | 19 model = "DH electronics STM32MP157C DHCOM Premium Developer Kit (2)";
|
| H A D | stm32mp157c-ed1-sp_min.dts | 9 model = "STMicroelectronics STM32MP157C eval daughter (SP_MIN)";
|
| H A D | stm32mp157c-dk2-sp_min.dts | 9 model = "STMicroelectronics STM32MP157C-DK2 Discovery Board (SP_MIN)";
|
| H A D | stm32mp157a-dk1-sp_min.dts | 9 model = "STMicroelectronics STM32MP157A-DK1 Discovery Board (SP_MIN)";
|
| H A D | stm32mp157c-ev1-sp_min.dts | 10 model = "STMicroelectronics STM32MP157C eval daughter on eval mother (SP_MIN)";
|
| H A D | stm32mp157c-ev1.dts | 11 model = "STMicroelectronics STM32MP157C eval daughter on eval mother";
|
| /rk3399_ARM-atf/plat/arm/board/fvp/fdts/ |
| H A D | optee_sp_manifest.dts | 31 run-time-model = <1>; /* SP pre-emptible. */
|