Searched refs:location (Results 1 – 22 of 22) sorted by relevance
| /arm-trusted-firmware-2.8.0/lib/semihosting/ |
| A D | semihosting.c | 33 ssize_t location; member
63 seek_block.location = offset; in semihosting_file_seek()
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/ |
| A D | arm-build-options.rst | 10 sets the TSP location to DRAM and ignores the ``ARM_TSP_RAM_LOCATION`` build
33 to the location of a device tree blob (DTB) already loaded in memory. The
52 location of the ROTPK hash returned by the function ``plat_get_rotpk_info()``
73 location of the ROTPK hash. Not expected to be a build option. This defaults to
78 - ``ARM_TSP_RAM_LOCATION``: location of the TSP binary. Options:
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | tools-build.rst | 9 indicate the location of the custom OpenSSL build. Then, to run the tools,
10 use the ``LD_LIBRARY_PATH`` to indicate the location of the built
|
| A D | docs-build.rst | 28 argument will install them locally, but you have to add their location to
|
| A D | image-terminology.rst | 58 location, then hand-off control to that image.
118 location, then hand-off control to that image. This may be performed in
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | hikey960.rst | 119 - Fetch that are used in recovery mode. The code location is in below.
|
| A D | stm32mp1.rst | 139 | default location (end of the first 128MB) is used when absent
|
| A D | rpi3.rst | 226 ``RPI3_DIRECT_LINUX_BOOT=1``. This option allows to specify the location of a
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | debugfs-design.rst | 58 - create(): create a file in a specific location.
|
| A D | romlib-design.rst | 48 affecting the order and location of functions already existing in the jump
|
| A D | arm-sip-service.rst | 165 filesystem location pointed to by path stored in `where`, using driver pointed
|
| A D | secure-partition-manager-mm.rst | 139 location of the binary that contains the BL32 image
211 through a shared memory region. The location of data in the shared memory area
625 a part of the Secure Partition image. The location of various sections in an
|
| A D | xlat-tables-lib-v2-design.rst | 211 arbitrary memory location. The user is still required to declare at compile-time
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | trusted-board-boot-build.rst | 45 In the case of Arm platforms, the location of the ROTPK hash must also be
|
| A D | reset-design.rst | 146 code in BL31 needs to know, or be able to determine, the location of the BL32
|
| A D | firmware-design.rst | 681 the platform code in BL31, or provided in a platform defined memory location
791 location by the Trusted Boot firmware, or passed from the Trusted Boot Firmware
1543 For BL31, a platform can specify an alternate location for NOBITS sections
1733 The location of the BL32 image will result in different memory maps. This is
2524 used to capture a timestamp at the location where it is used. The macro
|
| A D | auth-framework.rst | 652 CoT array, so the descriptors location in the array must match the identifiers.
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/juno/ |
| A D | index.rst | 130 - Save ``bl32.bin`` to a temporary location and clean the build products.
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | coding-style.rst | 394 location of the included header and reducing ambiguity in cases where generic
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | measured_boot_poc.rst | 53 OP-TEE knows the location of the Event Log by reading the DTB bindings
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model.rst | 400 | | | The list of images to load and their location is |
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | change-log.md | 726 …- fix location of fragment length check ([21ed9ea](https://review.trustedfirmware.org/plugins/giti…
2088 …- fix tool location path for byte_swape ([a89412a](https://review.trustedfirmware.org/plugins/giti…
5118 overlay. This patch creates a reserved location in SRAM for these
6248 location of the ROTPK is chosen at build-time using the `ARM_ROTPK_LOCATION`
6703 into DRAM instead of expecting this to be pre-loaded at known location. This
6707 that it knows the new location to execute from and no longer needs to copy
|
Completed in 50 milliseconds