Searched refs:package (Results 1 – 25 of 25) sorted by relevance
/trusted-firmware-a-3.7.0/ |
D | poetry.lock | 3 [[package]] 14 [[package]] 25 [package.dependencies] 28 [package.extras] 32 [[package]] 43 [package.dependencies] 46 [[package]] 57 [package.dependencies] 63 [package.extras] 69 [[package]] [all …]
|
/trusted-firmware-a-3.7.0/fdts/ |
D | stm32mp15xxac-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AC>; 66 st,package = <STM32MP_PKG_AC>;
|
D | stm32mp15xxaa-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AA>; 78 st,package = <STM32MP_PKG_AA>;
|
D | stm32mp15xxab-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AB>;
|
D | stm32mp15xxad-pinctrl.dtsi | 8 st,package = <STM32MP_PKG_AD>;
|
/trusted-firmware-a-3.7.0/docs/plat/ |
D | xilinx-zynqmp.rst | 96 The custom package can define the desired stack size as per the requirement in 137 (0xC2002000)(64-bit) to be used by a custom package for 143 - to use this service, custom package should implement their 144 smc handler with the name custom_smc_handler. once custom package is 148 Custom package makefile fragment inclusion in TF-A build 151 - custom package is not directly part of TF-A source. 154 custom package locally. 156 - custom package needs to implement makefile fragment named 159 - custom_pkg.mk specify all the rules to include custom package
|
D | hikey.rst | 124 - Remove the modemmanager package. This package may cause the idt tool failure.
|
D | hikey960.rst | 141 - Remove the modemmanager package. This package may causes hikey\_idt tool failure.
|
D | imx9.rst | 26 - Get the ELE FW image from NXP linux SDK package
|
/trusted-firmware-a-3.7.0/docs/resources/diagrams/plantuml/ |
D | io_arm_class_diagram.puml | 3 package arm_io_storage { 53 package IO {
|
/trusted-firmware-a-3.7.0/plat/st/stm32mp1/ |
D | stm32mp1_private.c | 341 uint32_t package; in get_cpu_package() local 343 if (stm32_get_otp_value(PACKAGE_OTP, &package) != 0) { in get_cpu_package() 347 package = (package & PACKAGE_OTP_PKG_MASK) >> in get_cpu_package() 350 return package; in get_cpu_package()
|
/trusted-firmware-a-3.7.0/docs/getting_started/ |
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:
|
D | prerequisites.rst | 74 source code, as it may not be available in the default package repositories. 87 source files (``.dts`` files). DTC is available for Linux through the package 92 The standard software package used for debugging software on Arm development
|
D | docs-build.rst | 5 `Sphinx`_ tool to build and package the plain-text documents into HTML-formatted
|
D | image-terminology.rst | 46 This is a packaging format used by TF-A to package firmware images in a single
|
D | build-options.rst | 862 package all secure partition blobs into the FIP. This file is not
|
/trusted-firmware-a-3.7.0/docs/tools/ |
D | memory-layout-tool.rst | 11 #. `Poetry`_ Python package manager
|
/trusted-firmware-a-3.7.0/docs/plat/nxp/ |
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
|
/trusted-firmware-a-3.7.0/docs/perf/ |
D | psci-performance-n1sdp.rst | 55 #. Using the fiptool, create a new FIP package and append the SCP ram image onto
|
/trusted-firmware-a-3.7.0/docs/plat/marvell/armada/ |
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:
|
/trusted-firmware-a-3.7.0/docs/components/ |
D | secure-partition-manager.rst | 354 Secure partitions are bundled as independent package files consisting 362 image payload. Each SP package is loaded independently by BL2 loader 365 The SP package identified by its UUID (matching FF-A uuid property) is 390 is processed by the dtc compiler to generate a DTB fed into the SP package. 392 the image and partition manifest within the SP package. Both offsets need to be 395 differ from 4KB, and to configure the regions allocated within the SP package, 480 address at which BL2 loaded the SP package. 627 The region for the boot information blob is allocated through the SP package. 629 .. image:: ../resources/diagrams/partition-package.png 650 The whole secure partition package image (see `Secure Partition packages`_) is
|
/trusted-firmware-a-3.7.0/docs/plat/arm/juno/ |
D | index.rst | 67 package included in the Linaro release:
|
/trusted-firmware-a-3.7.0/docs/process/ |
D | coding-guidelines.rst | 225 treated as a tightly integrated package; the image builder should be aware of
|
/trusted-firmware-a-3.7.0/docs/design/ |
D | firmware-design.rst | 2047 been added to the storage layer and allows a package to be read from supported 2058 payload data that has been appended to the end of the binary package. With the 2105 package. 2115 package that can be loaded by TF-A from platform storage. The tool currently 2124 The Firmware Image Package (FIP) driver can load images from a binary package on
|
/trusted-firmware-a-3.7.0/docs/ |
D | change-log.md | 5236 …- downgrade `package-lock.json` version ([7434b65](https://review.trustedfirmware.org/plugins/giti… 8441 `fip_create` tool to package the certificates in a FIP.
|