Searched refs:firmware (Results 1 – 25 of 107) sorted by relevance
12345
/trusted-firmware-a-latest/docs/ |
D | change-log.md | 6 ## [lts-2.10.4](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/refs/t… 10 …491e09](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/f491e09e66408… 18 …67271f](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/867271ff8135b… 24 …edbf2a](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/1edbf2ae58df6… 25 …609b0a](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/3609b0a953958… 26 …00931d](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/200931d2dcecd… 28 ## [lts-2.10.3](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/refs/t… 36 …fe6507](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/9fe65073d4425… 37 …24c800](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/a24c8006ea39b… 45 …6256d7](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/a6256d7a2638b… [all …]
|
/trusted-firmware-a-latest/docs/getting_started/ |
D | image-terminology.rst | 33 Clearly, many of these images are not BootLoaders, they are simply firmware 46 This is a packaging format used by TF-A to package firmware images in a single 48 platform-specific and may include TF-A images and other firmware images 57 and authenticate an updateable AP firmware image into an executable RAM 63 This is the 2nd stage AP firmware. It is currently also known as the "Trusted 65 required to load and authenticate all 3rd level firmware images into their 71 Also known as "SoC AP firmware" or "EL3 monitor firmware". Its primary purpose 107 This is the Realm-EL2 firmware. It is required if 117 and authenticate an updateable SCP firmware image into an executable RAM 119 conjunction with other processor firmware (for example, ``AP_BL1`` and [all …]
|
/trusted-firmware-a-latest/docs/plat/ |
D | synquacer.rst | 18 `link <https://github.com/ARM-software/arm-trusted-firmware>`__ 32 SCP firmware --> TF-A BL31 --> UEFI(edk2) 50 export WORKSPACE=$HOME/build/developerbox-firmware 58 git clone https://github.com/ARM-software/arm-trusted-firmware -b master 67 cd $WORKSPACE/arm-trusted-firmware 90 - The firmware image, which comprises the option ROM, ARM trusted firmware and 104 installed then you can adopt your the newly compiled system firmware using
|
D | qti-msm8916.rst | 22 It provides a minimal, community-maintained EL3 firmware and PSCI implementation, 34 The TF-A port is much more minimal compared to the original firmware and 54 BL31 (AArch64) or BL32/SP_MIN (AArch32) replaces the original ``tz`` firmware 61 the normal world bootloader was already loaded into RAM by a previous firmware 97 reports. This must be the same UART as used by earlier boot firmware since 105 The memory region used for the different firmware components is not fixed and 107 used by the original firmware (see ``platform.mk``): 111 * ``BL31_BASE``: Base address for the BL31 firmware component. Must point to 114 * ``BL32_BASE``: Base address for the BL32 firmware component. 126 but it provides the firmware with required metadata. [all …]
|
D | brcm-stingray.rst | 7 Trusted Firmware-A (TF-A) is used to implement secure world firmware, supporting 21 `link <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/>`__
|
D | qemu-sbsa.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for QEMU SBSA 27 git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git tfa 36 git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git tfa
|
D | ti-k3.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for Texas Instruments K3 SoCs. 24 https://github.com/ARM-software/arm-trusted-firmware.git
|
D | qti.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for QTI SC7180, 21 `link <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`__
|
/trusted-firmware-a-latest/docs/components/ |
D | mpmm.rst | 11 |MPMM| is enabled on a per-core basis by the EL3 runtime firmware. The presence 12 of |MPMM| cannot be determined at runtime by the firmware, and therefore the 29 runtime firmware - please see :ref:`Activity Monitor Auxiliary Counters` for
|
D | index.rst | 14 firmware-update
|
D | debugfs-design.rst | 10 The *DebugFS* feature is primarily aimed at exposing firmware debug data to 20 The implementation permits exposing virtual files, firmware drivers, and file blobs. 71 measurements through a file, and internal firmware state counters through 73 - This permits direct access to a firmware driver, mainly for test purposes 105 - Notice, a physical device driver if exposed by the firmware may conflict with
|
/trusted-firmware-a-latest/ |
D | .gitreview | 4 project=TF-A/trusted-firmware-a
|
D | pyproject.toml | 2 name = "trusted-firmware-a"
|
/trusted-firmware-a-latest/plat/arm/board/morello/fdts/ |
D | morello_nt_fw_config.dts | 28 * Placeholder for firmware-version node with default values. 32 firmware-version {
|
/trusted-firmware-a-latest/docs/about/ |
D | features.rst | 62 Firmware encryption and packaging of the various firmware images into a 65 - Measured boot support with PoC to showcase its interaction with firmware TPM 70 - Following firmware update mechanisms available: 85 interrupts to their registered handlers, to facilitate firmware-first 88 - A dynamic configuration framework that enables each of the firmware images 91 as part of the FIP, to be passed through the firmware stages. 92 This feature is now incorporated inside the firmware configuration framework 96 the EL3 Runtime Software is loaded using other firmware or a separate 100 - Support for Errata management firmware interface.
|
/trusted-firmware-a-latest/docs/plat/arm/morello/ |
D | index.rst | 5 The platform port present at `site <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`_ 18 firmware image (the FIP image) from the AP QSPI NOR Flash Memory into the 24 firmware. Execution is finally handed off to AP_BL33, which is the non-secure
|
/trusted-firmware-a-latest/plat/arm/board/fvp/fdts/ |
D | fvp_fw_config.dts | 29 * Load SoC and TOS firmware configs at the base of 31 * overlap BL2, BL31 or BL32. The NT firmware config
|
/trusted-firmware-a-latest/docs/security_advisories/ |
D | security-advisory-tfv-2.rst | 58 .. _commit 495f3d3: https://github.com/ARM-software/arm-trusted-firmware/commit/495f3d3 59 .. _AArch64 macro: https://github.com/ARM-software/arm-trusted-firmware/blob/bcc2bf0/include/common… 60 .. _AArch32 equivalent: https://github.com/ARM-software/arm-trusted-firmware/blob/bcc2bf0/include/c… 61 .. _Pull Request #841: https://github.com/ARM-software/arm-trusted-firmware/pull/841
|
D | security-advisory-tfv-5.rst | 54 .. _Pull Request #1127: https://github.com/ARM-software/arm-trusted-firmware/pull/1127 55 .. _Commit e290a8fcbc: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=e290a… 56 .. _Commit c3e8b0be9b: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=c3e8b…
|
D | security-advisory-tfv-7.rst | 36 new firmware interfaces, for example the `Software Delegated Exception Interface 88 the default mitigation state for firmware-managed execution contexts is enabled. 105 …n vulnerabilities: https://developer.arm.com/cache-speculation-vulnerability-firmware-specification 106 .. _Pull Request #1392: https://github.com/ARM-software/arm-trusted-firmware/pull/1392 107 .. _Pull Request #1397: https://github.com/ARM-software/arm-trusted-firmware/pull/1397
|
D | security-advisory-tfv-6.rst | 59 (to execute firmware branch predictor invalidation), then there is a dependency 71 the normal world to discover the presence of this firmware service. 144 .. _Pull Request #1214: https://github.com/ARM-software/arm-trusted-firmware/pull/1214 145 .. _Pull Request #1228: https://github.com/ARM-software/arm-trusted-firmware/pull/1228 146 .. _Pull Request #1240: https://github.com/ARM-software/arm-trusted-firmware/pull/1240 147 .. _Pull Request #1405: https://github.com/ARM-software/arm-trusted-firmware/pull/1405 148 …ion specification: https://developer.arm.com/cache-speculation-vulnerability-firmware-specification
|
/trusted-firmware-a-latest/docs/design/ |
D | index.rst | 11 firmware-design
|
/trusted-firmware-a-latest/docs/threat_model/ |
D | threat_model_rss_interface.rst | 16 the AP core. The threat model for the RSS firmware will be provided by the RSS 17 firmware project in the future. 48 allowed only for firmware running at EL3. Accidentally exposing this
|
/trusted-firmware-a-latest/include/plat/arm/common/ |
D | fconf_ethosn_getter.h | 30 struct ethosn_allocator_t firmware; member
|
/trusted-firmware-a-latest/docs/plat/arm/corstone1000/ |
D | index.rst | 14 The board boot relies on CoT (chain of trust). The trusted-firmware-a 23 BL2 performs the actions described in the trusted-firmware-a TBB design
|
12345