Searched refs:model (Results 1 – 25 of 56) sorted by relevance
123
| /trusted-firmware-a-latest/plat/rpi/rpi3/ |
| D | rpi3_bl1_setup.c | 72 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-latest/docs/threat_model/ |
| D | index.rst | 8 platform's needs, providing a holistic threat model covering all of its features
10 documents which, together, form the project's threat model. These are
15 As the TF-A codebase evolves and new features get added, these threat model
21 Although our aim is eventually to provide threat model material for all
43 …: https://docs.microsoft.com/en-us/azure/security/develop/threat-modeling-tool-threats#stride-model
|
| D | threat_model_fvp_r.rst | 7 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`
|
| D | threat_model_rss_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 RSS and
16 the AP core. The threat model for the RSS firmware will be provided by the RSS
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
|
| 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 …]
|
| 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. |
|
| /trusted-firmware-a-latest/plat/allwinner/common/ |
| D | sunxi_bl31_setup.c | 143 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-latest/docs/design/ |
| 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 …]
|
| /trusted-firmware-a-latest/fdts/ |
| D | stm32mp157a-dk1.dts | 15 model = "STMicroelectronics STM32MP157A-DK1 Discovery Board";
|
| D | corstone700_fpga.dts | 12 model = "corstone700-fpga";
|
| D | stm32mp157c-dk2.dts | 16 model = "STMicroelectronics STM32MP157C-DK2 Discovery Board";
|
| D | corstone700_fvp.dts | 12 model = "corstone700-fvp";
|
| D | stm32mp257f-ev1.dts | 15 model = "STMicroelectronics STM32MP257F-EV1 Evaluation Board";
|
| D | stm32mp157c-odyssey.dts | 13 model = "Seeed Studio Odyssey-STM32MP157C Board";
|
| D | stm32mp157a-dhcor-avenger96.dts | 21 model = "Arrow Electronics STM32MP157A Avenger96 board";
|
| D | stm32mp157c-dhcom-pdk2.dts | 19 model = "DH electronics STM32MP157C DHCOM Premium Developer Kit (2)";
|
| D | stm32mp157c-ev1.dts | 11 model = "STMicroelectronics STM32MP157C eval daughter on eval mother";
|
| D | n1sdp-single-chip.dts | 11 model = "Arm Neoverse N1 System Development Platform";
|
| D | stm32mp157c-lxa-mc1.dts | 16 model = "Linux Automation MC-1 board";
|
| D | fvp-ve-Cortex-A7x1.dts | 14 model = "V2F-1XV7 Cortex-A7x1 SMM";
|
| D | arm_fpga.dts | 16 model = "ARM FPGA";
|
| /trusted-firmware-a-latest/plat/arm/board/fvp/fdts/ |
| D | optee_sp_manifest.dts | 30 run-time-model = <1>; /* SP pre-emptible. */
|
| /trusted-firmware-a-latest/docs/plat/arm/fvp/ |
| D | index.rst | 8 documentation for a detailed description of the model parameter options.
95 Since FVP model Version 11.0 Build 11.0.34 and Version 8.5 Build 0.8.5202
174 Therefore, one must modify the way the model is normally invoked in order to
185 using the following model parameters:
192 To provide the model with the EL3 payload image, the following methods may be
196 flash memory. On Base Cortex and AEM FVPs, the following model parameter
215 model parameters:
384 and enable the GICv3 device in the model. Note that without this option,
449 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
467 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to
[all …]
|
| /trusted-firmware-a-latest/docs/ |
| D | index.rst | 38 Armv8-A model and hardware platforms.
76 **Platform Ports** provides a list of the supported hardware and software-model
|
| /trusted-firmware-a-latest/include/drivers/ |
| D | raw_nand.h | 110 uint8_t model[20]; member
|
123
