Home
last modified time | relevance | path

Searched refs:was (Results 1 – 25 of 43) sorted by relevance

12

/rk3399_ARM-atf/docs/plat/qti/
H A Dmsm8916.rst61 the normal world bootloader was already loaded into RAM by a previous firmware
162 INFO: BL31: cortex_a53: CPU workaround for 819472 was applied
163 INFO: BL31: cortex_a53: CPU workaround for 824069 was applied
164 INFO: BL31: cortex_a53: CPU workaround for 826319 was applied
165 INFO: BL31: cortex_a53: CPU workaround for 827319 was applied
166 INFO: BL31: cortex_a53: CPU workaround for 835769 was applied
167 INFO: BL31: cortex_a53: CPU workaround for disable_non_temporal_hint was applied
168 INFO: BL31: cortex_a53: CPU workaround for 843419 was applied
169 INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied
191 INFO: BL32: cortex_a53: CPU workaround for 819472 was applied
[all …]
H A Dchrome.rst38 is picked. qtiseclib with stub implementation doesn't boot device. This was
/rk3399_ARM-atf/
H A Ddco.txt17 (a) The contribution was created in whole or in part by me and I
29 (c) The contribution was provided directly to me by some other
/rk3399_ARM-atf/lib/zlib/
H A Dinflate.h125 unsigned was; /* initial length of match */ member
H A Dcrc32.c260 int was; in test_and_set() local
262 was = *flag; in test_and_set()
264 return was; in test_and_set()
/rk3399_ARM-atf/docs/plat/
H A Dnpcm845x.rst12 This SoC was tested on the Arbel NPCM845X evaluation board.
H A Dintel-stratix10.rst90 WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing!
H A Drpi5.rst61 ``kernel_address=`` and ``device_tree_address=`` in config.txt. If TF-A was built
/rk3399_ARM-atf/docs/security_advisories/
H A Dsecurity-advisory-tfv-4.rst52 #678`_ was merged (on 18 August 2016). However, the upstream code was not
53 vulnerable until `Pull Request #939`_ was merged (on 22 May 2017), which
55 then, the ``check_uptr_overflow()`` macro was not used in AArch32 code.
H A Dsecurity-advisory-tfv-5.rst51 whereas the EL3 was fixed in the later commits.
/rk3399_ARM-atf/docs/getting_started/
H A Dimage-terminology.rst22 - Previously, the format for 3rd level images had 2 forms; ``BL3`` was either
24 subscript number, depending on whether rich text formatting was available.
25 This was confusing and often the dash gets omitted in practice. Therefore the
122 This image was previously abbreviated as ``BL0`` but in some systems, the SCP
134 This image was previously abbreviated as BL3-0 but from the SCP's point of view,
/rk3399_ARM-atf/docs/components/spd/
H A Doptee-dispatcher.rst12 boot via an SMC call by enabling the option for OPTEE_ALLOW_SMC_LOAD that was
/rk3399_ARM-atf/docs/perf/
H A Dpsci-performance-methodology.rst14 was used because the results in the debug build became skewed; the console
H A Dpsci-performance-instr.rst112 was requested, it is captured in the warm boot path.
/rk3399_ARM-atf/docs/components/
H A Dsecure-partition-manager-mm.rst175 ``e29efeb1b4``, in which the port for FVP was introduced.
500 was made to signal either completion of Secure Partition initialisation or
518 Zero or a positive value indicates that the event was handled successfully.
519 The values depend upon the original event that was delegated to the Secure
522 - ``SUCCESS`` : Used to indicate that the Secure Partition was initialised
523 or a runtime request was handled successfully.
545 - ``NOT_SUPPORTED``: Function was called from the Non-secure world.
581 completion of a request that was delegated to it by the SPM.
589 system register values when the call was made.
691 function was called from the Non-secure world. Also returned if it is
[all …]
H A Dven-el3-service.rst67 FID changes or the FID that was allocated for discovery changes. So any breaking subfeature
H A Darm-sip-service.rst75 registers should not be expected to hold their values before the call was made.
/rk3399_ARM-atf/docs/design/
H A Dinterrupt-framework-design.rst325 exception level when the interrupt was generated. A value of ``1`` means
326 that it was in the non-secure state. A value of ``0`` indicates that it was
328 interrupt was generated and routed as per the routing model specified
693 #. Validating the interrupt. This involves ensuring that the interrupt was
697 the interrupt was taken from to determine this. If the interrupt is not
710 if the security state of the execution context where the interrupt was
752 exception level and the security state from where the Secure-EL1 interrupt was
774 ``TSP_HANDLE_SEL1_INTR_AND_RETURN``. If the TSP was preempted earlier by a non
845 handling Secure-EL1 interrupts that triggered while execution was in the normal
885 #. Checks whether the TSP needs a resume i.e check if it was preempted. It
[all …]
/rk3399_ARM-atf/drivers/renesas/common/ddr/ddr_b/
H A Dboot_init_dram_config.c2005 #error Invalid value was set to RCAR_DRAM_MEMRANK in ddr_rank_judge()
/rk3399_ARM-atf/docs/design_documents/
H A Dmeasured_boot_poc.rst39 needed to test that the Event Log was properly created. One of these images will
44 for convenience. As the fTPM service used is an OP-TEE TA, it was easy to add
52 Support to interfacing with Measured Boot was added to version 3.9.0 of
62 reference implementation from Microsoft. The service was updated in order
H A Drse.rst57 that data was read. Signalling happens via IRQ. If the message is longer than
230 semantics. This means that measurements are not stored directly (as it was
268 - ``Measurement algorithm``: Optional. The hash algorithm which was used to
431 Delegated Attestation Service was mainly developed to support the attestation
/rk3399_ARM-atf/docs/plat/nxp/
H A Dnxp-ls-fuse-prov.rst28 - At U-Boot prompt, verify that SNVS register - HPSR, whether OTPMK was written, already:
/rk3399_ARM-atf/docs/process/
H A Dcommit-style.rst19 - How was it tested?
/rk3399_ARM-atf/docs/plat/marvell/armada/
H A Dporting.rst123 The porting layer for PHY was introduced in TF-A. There is one file
/rk3399_ARM-atf/make_helpers/
H A Dbuild_macros.mk271 …$(if $(wildcard $(value $(_V))),,$$$$(error '$(_V)=$(value $(_V))' was specified, but '$(value $(_…

12