Searched refs:package (Results 1 – 20 of 20) sorted by relevance
/arm-trusted-firmware-2.8.0/fdts/ |
A D | stm32mp15xxac-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AC>; 66 st,package = <STM32MP_PKG_AC>;
|
A D | stm32mp15xxaa-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AA>; 78 st,package = <STM32MP_PKG_AA>;
|
A D | stm32mp15xxab-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AB>;
|
A D | stm32mp15xxad-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AD>;
|
/arm-trusted-firmware-2.8.0/docs/resources/diagrams/plantuml/ |
A D | io_arm_class_diagram.puml | 3 package arm_io_storage { 53 package IO {
|
/arm-trusted-firmware-2.8.0/plat/st/stm32mp1/ |
A D | stm32mp1_private.c | 366 uint32_t package; in get_cpu_package() local 368 if (stm32_get_otp_value(PACKAGE_OTP, &package) != 0) { in get_cpu_package() 372 package = (package & PACKAGE_OTP_PKG_MASK) >> in get_cpu_package() 375 return package; in get_cpu_package()
|
/arm-trusted-firmware-2.8.0/docs/getting_started/ |
A D | tools-build.rst | 71 Example 1: create a new Firmware package ``fip.bin`` that contains BL2 and BL31: 80 Example 2: view the contents of an existing Firmware package: 86 Example 3: update the entries of an existing Firmware package: 95 Example 4: unpack all entries from an existing Firmware package: 102 Example 5: remove an entry from an existing Firmware package:
|
A D | prerequisites.rst | 68 source code, as it may not be available in the default package repositories. 81 source files (``.dts`` files). DTC is available for Linux through the package 86 The standard software package used for debugging software on Arm development
|
A D | docs-build.rst | 5 `Sphinx`_ tool to build and package the plain-text documents into HTML-formatted
|
A D | image-terminology.rst | 46 This is a packaging format used by TF-A to package firmware images in a single
|
A D | build-options.rst | 843 package all secure partition blobs into the FIP. This file is not
|
/arm-trusted-firmware-2.8.0/docs/plat/ |
A D | hikey.rst | 124 - Remove the modemmanager package. This package may cause the idt tool failure.
|
A D | hikey960.rst | 141 - Remove the modemmanager package. This package may causes hikey\_idt tool failure.
|
/arm-trusted-firmware-2.8.0/docs/plat/nxp/ |
A D | nxp-layerscape.rst | 24 comes preloaded with a board support package (BSP) based on a standard Linux 58 in a flexible I/O package supporting fanless designs. This SoC is a 145 comes pre-loaded with a board support package (BSP) based on a standard
|
/arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
A D | build.rst | 129 package: 1 or 2 depending on the SoC used. The parameter is valid for OcteonTX2 CN913x SoC 238 Look at Armada37x0 chip package marking on board to identify correct CPU frequency. 239 The last line on package marking (next line after the 88F37x0 line) should contain:
|
/arm-trusted-firmware-2.8.0/docs/components/ |
A D | secure-partition-manager.rst | 339 Secure partitions are bundled as independent package files consisting 347 image payload. Each SP package is loaded independently by BL2 loader 350 The SP package identified by its UUID (matching FF-A uuid property) is 375 is processed by the dtc compiler to generate a DTB fed into the SP package. 377 the image and partition manifest within the SP package. Both offsets need to be 380 differ from 4KB, and to configure the regions allocated within the SP package, 465 address at which BL2 loaded the SP package. 600 The region for the boot information blob is allocated through the SP package. 602 .. image:: ../resources/diagrams/partition-package.png 623 The whole secure partition package image (see `Secure Partition packages`_) is
|
/arm-trusted-firmware-2.8.0/docs/plat/arm/juno/ |
A D | index.rst | 67 package included in the Linaro release:
|
/arm-trusted-firmware-2.8.0/docs/process/ |
A D | coding-guidelines.rst | 225 treated as a tightly integrated package; the image builder should be aware of
|
/arm-trusted-firmware-2.8.0/docs/design/ |
A D | firmware-design.rst | 1950 been added to the storage layer and allows a package to be read from supported 1961 payload data that has been appended to the end of the binary package. With the 2008 package. 2018 package that can be loaded by TF-A from platform storage. The tool currently 2027 The Firmware Image Package (FIP) driver can load images from a binary package on
|
/arm-trusted-firmware-2.8.0/docs/ |
A D | change-log.md | 3068 …- downgrade `package-lock.json` version ([7434b65](https://review.trustedfirmware.org/plugins/giti… 6273 `fip_create` tool to package the certificates in a FIP.
|
Completed in 33 milliseconds