| /rk3399_ARM-atf/plat/arm/board/tc/fdts/ |
| H A D | tc_spmc_common_sp_manifest.dtsi | 8 * Secure world memory map. For a full view of the DRAM map, see platform_def.h
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | tsp.rst | 9 must be recompiled as well. For more information on SPs and SPDs, see the
|
| H A D | psci-performance-n1sdp.rst | 12 Please see the Runtime Instrumentation :ref:`Testing Methodology
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | mpmm.rst | 20 runtime firmware - please see :ref:`Activity Monitor Auxiliary Counters` for
|
| H A D | sdei.rst | 126 ``OR``\ ed to form parameters to macros that define events (see
236 bound or dynamic events can't be explicitly dispatched (see the section below).
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | fconf_properties.rst | 24 If secondary-load-address is also provided (see below), then this is the
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | docs-build.rst | 53 directory of the project, run the following command to see the supported
98 other use cases, please see the official `Poetry`_ documentation.
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-10.rst | 113 child certificate (see ``auth_hash()``).
116 authenticity and integrity (see ``auth_signature()``).
119 it from unauthorized rollback to a previous version (see ``auth_nvctr()``).
|
| H A D | security-advisory-tfv-13.rst | 25 | | Also see mitigation guidance in the `Official Arm Advisory`_ |
|
| H A D | security-advisory-tfv-7.rst | 83 on exit from EL3. For more information on this approach, see `Firmware
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | contact.rst | 25 You can see a `summary of all the lists`_ on the TrustedFirmware.org website.
|
| H A D | features.rst | 5 description of these features and their implementation details, please see
|
| H A D | lts.rst | 115 taking into account the test-and-debug phase before LTS is cut (see below) --
140 members, see the project charter for more details). This automated test coverage
399 adapt it as we see practical problems.
|
| /rk3399_ARM-atf/tools/nxp/create_pbl/ |
| H A D | README | 40 -c SoC Number (see description above)
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 9 which focuses on the most common configuration we expect to see. The other
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | msm8916.rst | 71 CPUs that only support AArch32 (see table above). For all others AArch64 is the
99 the usual debug UART used for the platform (see ``platform.mk``).
107 used by the original firmware (see ``platform.mk``):
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | rz-g2.rst | 71 reference tree [1] resets into EL1 before entering BL2 - see its
83 PARAMS_BASE instead of using registers to get to those locations (see
|
| H A D | rcar-gen3.rst | 71 reference tree [1] resets into EL1 before entering BL2 - see its
88 PARAMS_BASE instead of using registers to get to those locations (see
|
| H A D | rpi4.rst | 48 see some text from BL31, followed by the output of the EL2 payload.
|
| H A D | rpi3.rst | 136 instructions to see how to do it. This system is strongly discouraged.
432 to it (for example, with ``screen /dev/ttyUSB0 115200``) you should see some
433 text. In the case of an AArch32 kernel, you should see something like this:
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | uart-booting.rst | 40 After that immediately start terminal on ``/dev/ttyUSB<port#>`` to see boot output.
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | measured_boot_poc.rst | 408 Following up with the fTPM startup process, we can see that all the
437 (see the field ``AlgorithmId`` on the logs above):
468 because the boot process records all the images in this PCR (see field ``PCRIndex``
486 the build environment variable ``FTPM_FLAGS`` (see ``<toolkit_home>/build/common.mk``)
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 86 types are supported for GIC version 2.0 (Arm GICv2) (see `Assumptions in
300 This section describes in detail the role of each software component (see
518 (see `Valid routing models`_) effects the implementation of the Secure-EL1
614 This section describes in detail the role of each software component (see
779 (see section `Test secure payload dispatcher behavior`_).
808 the secure CPU context (see step 3 above) in case the TSP had been preempted
837 option ``TSP_NS_INTR_ASYNC_PREEMPT`` (see Section `Test secure payload
878 (see section `Implication of preempted SMC on Non-Secure Software`_). The TSPD
966 identifier from the non-secure state (see section `Test secure payload
|
| /rk3399_ARM-atf/make_helpers/ |
| H A D | constraints.mk | 197 $(error Error: PAUTH_LR cannot be used without PAUTH (see BRANCH_PROTECTION))
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | commit-style.rst | 91 can, or add their own if no appropriate one exists (see :ref:`Adding Scopes`).
|