| /trusted-firmware-a/ |
| A D | dco.txt | 17 (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
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_downloads/64c40a63b9b2c30373557926065e7bb2/ |
| A D | dco.txt | 17 (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
|
| /trusted-firmware-a/docs/security_advisories/ |
| A D | security-advisory-tfv-4.rst | 52 #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.
|
| A D | security-advisory-tfv-5.rst | 51 whereas the EL3 was fixed in the later commits.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/ |
| A D | security-advisory-tfv-4.rst.txt | 52 #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.
|
| A D | security-advisory-tfv-5.rst.txt | 51 whereas the EL3 was fixed in the later commits.
|
| /trusted-firmware-a/lib/zlib/ |
| A D | inflate.h | 124 unsigned was; /* initial length of match */ member
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | image-terminology.rst | 22 - 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
113 This image was previously abbreviated as ``BL0`` but in some systems, the SCP
125 This image was previously abbreviated as BL3-0 but from the SCP's point of view,
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | image-terminology.rst.txt | 22 - 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
113 This image was previously abbreviated as ``BL0`` but in some systems, the SCP
125 This image was previously abbreviated as BL3-0 but from the SCP's point of view,
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | qti.rst.txt | 37 is picked. qtiseclib with stub implementation doesn't boot device. This was
|
| A D | intel-stratix10.rst.txt | 90 WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing!
|
| /trusted-firmware-a/docs/plat/ |
| A D | qti.rst | 37 is picked. qtiseclib with stub implementation doesn't boot device. This was
|
| A D | intel-stratix10.rst | 90 WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing!
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | sphinx.sty | 205 % caption package, whether the latter was loaded before or after sphinx.
211 % in presence of caption package, drop our own \sphinxcaption whose aim was to
245 % It was passed "warn" option from latex template in case it is already loaded
315 % #1=label of footnote text, #2=page number where footnote text was printed
|
| A D | sphinxpackagefootnote.sty | 340 % - the footnote was explicitly numbered in sources,
341 % - or it was in restrained context and is rendered using footnotetext
355 % #1=label for reference, #2=page where footnote was printed
|
| A D | sphinxlatextables.sty | 44 % \X was chosen to avoid possibility of conflict
224 % cells (the code does inserts & tokens, see TN1b). It was decided to keep it
250 \def\sphinx@TYI@stop@multicolumn{\egroup % varwidth was used with \tymax
451 \endgroup % group was opened in \sphinxmultirow
|
| /trusted-firmware-a/docs/components/ |
| A D | secure-partition-manager-mm.rst | 182 ``e29efeb1b4``, in which the port for FVP was introduced.
507 was made to signal either completion of Secure Partition initialisation or
525 Zero or a positive value indicates that the event was handled successfully.
526 The values depend upon the original event that was delegated to the Secure
529 - ``SUCCESS`` : Used to indicate that the Secure Partition was initialised
530 or a runtime request was handled successfully.
552 - ``NOT_SUPPORTED``: Function was called from the Non-secure world.
588 completion of a request that was delegated to it by the SPM.
596 system register values when the call was made.
691 function was called from the Non-secure world. Also returned if it is
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | secure-partition-manager-mm.rst.txt | 182 ``e29efeb1b4``, in which the port for FVP was introduced.
507 was made to signal either completion of Secure Partition initialisation or
525 Zero or a positive value indicates that the event was handled successfully.
526 The values depend upon the original event that was delegated to the Secure
529 - ``SUCCESS`` : Used to indicate that the Secure Partition was initialised
530 or a runtime request was handled successfully.
552 - ``NOT_SUPPORTED``: Function was called from the Non-secure world.
588 completion of a request that was delegated to it by the SPM.
596 system register values when the call was made.
691 function was called from the Non-secure world. Also returned if it is
[all …]
|
| /trusted-firmware-a/docs/design/ |
| A D | interrupt-framework-design.rst | 325 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 …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | interrupt-framework-design.rst.txt | 325 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 …]
|
| /trusted-firmware-a/drivers/renesas/common/ddr/ddr_b/ |
| A D | boot_init_dram_config.c | 2005 #error Invalid value was set to RCAR_DRAM_MEMRANK in ddr_rank_judge()
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/perf/ |
| A D | psci-performance-juno.rst.txt | 38 When using the debug build of TF, there was no noticeable difference in the
42 framework was used because the results in the debug build became skewed; the
|
| /trusted-firmware-a/docs/perf/ |
| A D | psci-performance-juno.rst | 38 When using the debug build of TF, there was no noticeable difference in the
42 framework was used because the results in the debug build became skewed; the
|
| /trusted-firmware-a/docs/design_documents/ |
| A D | measured_boot_poc.rst | 37 needed to test that the Event Log was properly created. One of these images will
42 for convenience. As the fTPM service used is an OP-TEE TA, it was easy to add
50 Support to interfacing with Measured Boot was added to version 3.9.0 of
60 reference implementation from Microsoft. The service was updated in order
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design_documents/ |
| A D | measured_boot_poc.rst.txt | 37 needed to test that the Event Log was properly created. One of these images will
42 for convenience. As the fTPM service used is an OP-TEE TA, it was easy to add
50 Support to interfacing with Measured Boot was added to version 3.9.0 of
60 reference implementation from Microsoft. The service was updated in order
|