| /rk3399_ARM-atf/include/lib/hob/ |
| H A D | mpinfo.h | 105 struct efi_cpu_physical_location location; member
|
| /rk3399_ARM-atf/lib/semihosting/ |
| H A D | semihosting.c | 33 ssize_t location; member
63 seek_block.location = offset; in semihosting_file_seek()
|
| /rk3399_ARM-atf/fdts/ |
| H A D | tc-fpga.dtsi | 33 * android image will be side loaded to this location
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | xilinx-zynqmp.rst | 50 For DEBUG=1 configuration for ZynqMP the BL31_BASE is set to the DDR location
51 of 0x1000 and BL31_LIMIT is set to DDR location of 0x7FFFF. By default the
64 If the user wants to move the bl31 to a different DDR location, user can provide
65 the DDR address location using the build time parameters ZYNQMP_ATF_MEM_BASE and
153 - <CUSTOM_PKG_PATH> is the location at which user clones a
|
| H A D | amd-versal2.rst | 77 - ``<CUSTOM_PKG_PATH>`` is the location where the user clones a
|
| H A D | hikey960.rst | 119 - Fetch that are used in recovery mode. The code location is in below.
|
| H A D | s32g274a.rst | 52 The ``DDR_FW_BIN_PATH`` parameter must point to the location of the folder
|
| H A D | xilinx-versal.rst | 94 - ``<CUSTOM_PKG_PATH>`` is the location where the user clones a
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-13.rst | 6 | | prefetch engine to fetch the contents of a privileged location |
35 to fetch the contents of a privileged location (for which it
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | fconf_properties.rst | 38 another location during the boot-flow.
|
| /rk3399_ARM-atf/docs/plat/arm/ |
| H A D | arm-build-options.rst | 10 sets the TSP location to DRAM and ignores the ``ARM_TSP_RAM_LOCATION`` build
38 or ``ARM_PRELOADED_DTB_BASE`` option must specify the memory location of a
63 location of the ROTPK returned by the function ``plat_get_rotpk_info()``
94 - ``ARM_TSP_RAM_LOCATION``: location of the TSP binary. Options:
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H 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
|
| H 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
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mpus.rst | 56 | default location (end of the first 128MB) is used when absent
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | ven-el3-debugfs.rst | 75 filesystem location pointed to by path stored in `where`, using driver pointed
|
| H A D | debugfs-design.rst | 58 - create(): create a file in a specific location.
|
| H A D | romlib-design.rst | 48 affecting the order and location of functions already existing in the jump
|
| H A D | secure-partition-manager-mm.rst | 132 location of the binary that contains the BL32 image
204 through a shared memory region. The location of data in the shared memory area
618 a part of the Secure Partition image. The location of various sections in an
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rdaspen.rst | 53 into Trusted SRAM and passes its location to BL31.
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_firmware_handoff.rst | 128 | | stage relocates a TL from one location to another |
|
| H A D | threat_model.rst | 830 | | | The list of images to load and their location is |
946 (location of the client).
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | trusted-board-boot-build.rst | 44 In the case of Arm platforms, the location of the ROTPK must also be
|
| H A D | reset-design.rst | 147 location of the BL32 (if required) and BL33 images and provide this information
|
| /rk3399_ARM-atf/docs/plat/arm/juno/ |
| H A D | index.rst | 130 - Save ``bl32.bin`` to a temporary location and clean the build products.
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | coding-style.rst | 418 location of the included header and reducing ambiguity in cases where generic
|