| /arm-trusted-firmware-2.8.0/include/lib/libc/ |
| A D | assert.h | 20 # define assert(e) ((e) ? (void)0 : __assert(__FILE__, __LINE__)) argument
22 # define assert(e) ((e) ? (void)0 : __assert()) argument
25 #define assert(e) ((void)0) argument
|
| /arm-trusted-firmware-2.8.0/plat/nxp/common/soc_errata/ |
| A D | errata.mk | 24 $(foreach e,$(ERRATA),$(eval $(call enable_errata,$(strip $(e)))))
|
| /arm-trusted-firmware-2.8.0/tools/cert_create/src/ |
| A D | key.c | 54 BIGNUM *e; in key_create_rsa()
57 e = BN_new(); in key_create_rsa()
58 if (e == NULL) { in key_create_rsa()
63 if (!BN_set_word(e, RSA_F4)) { in key_create_rsa()
74 if (!RSA_generate_key_ex(rsa, key_bits, e, NULL)) { in key_create_rsa()
84 BN_free(e); in key_create_rsa()
90 BN_free(e); in key_create_rsa()
|
| /arm-trusted-firmware-2.8.0/include/export/ |
| A D | README | 7 - All definitions should be sufficiently namespaced (e.g. with BL_ or TF_) to
14 in the ISO C standard (i.e. uint64_t is fine, but not u_register_t). They
20 pre-defined by all common compilers (e.g. __ASSEMBLER__ or __aarch64__).
25 (e.g. long, uintptr_t, pointer types) where possible. (Some existing export
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | measured_boot_poc.rst | 234 M/TA: : 6b 2e d2 8c c9 36 92 7d 46 c5 b9 c3 a4 6c 51 7c
243 M/TA: : e5 de e7 7e 99 17 52 12 7d f7 45 ca 4f 4a 39 c0
251 M/TA: Digest : 4e e4 8e 5a e6 50 ed e0 b5 a3 54 8a 1f d6 0e 8a
252 M/TA: : ea 0e 71 75 0e a4 3f 82 76 ce af cd 7c b0 91 e0
261 M/TA: : f8 19 ec 6e 1e ec 73 ba 5a be d0 96 e3 5f 6d 75
270 M/TA: : d9 6e 93 98 2d 40 87 96 1b 5a a7 ee f1 f4 40 63
279 M/TA: : 00 0f 38 dc 8e c8 02 cd 79 f2 48 d2 2c 25 ab e2
345 NOTICE: : 6b 2e d2 8c c9 36 92 7d 46 c5 b9 c3 a4 6c 51 7c
362 NOTICE: Digest : 4e e4 8e 5a e6 50 ed e0 b5 a3 54 8a 1f d6 0e 8a
363 NOTICE: : ea 0e 71 75 0e a4 3f 82 76 ce af cd 7c b0 91 e0
[all …]
|
| A D | cmake_framework.rst | 31 * CMake has various advantages over Make, e.g.:
36 * Out-of-the-box support for integration with several tools (e.g. project
41 * Language is problematic (e.g. variable scope).
71 configuration management tool (e.g. Kconfig) shall be used to generate these
78 targets, i.e. what is the build output, what source files are used, what
81 the previous section. A group can be applied onto a target, i.e. a collection of
89 that CMake does not solve (e.g. preprocessing a file). For these tasks the
95 In the TF-A buildsystem some external tools are used, e.g. fiptool for image
108 In the provisioning phase, first we have to obtain the necessary resources, i.e.
|
| /arm-trusted-firmware-2.8.0/include/drivers/nxp/crypto/caam/ |
| A D | rsa.h | 22 uint8_t *e; member
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | debugfs-design.rst | 27 - # is used as root for drivers (e.g. #t0 is the first uart)
28 - / is used as root for virtual "files" (e.g. /fip, or /dev/uart)
70 - Debug data can be partitioned into different virtual files e.g. expose PMF
74 (e.g. a hardware device that may not be accessible to non-privileged/
82 shared buffer is used to pass path string parameters, or e.g. to exchange
|
| A D | mpmm.rst | 8 triggering of whole-rail (i.e. clock chopping) responses to overcurrent
|
| A D | sdei.rst | 78 To define an event that's meant to be explicitly dispatched (i.e., not as a
183 - For those interrupts that are statically bound (i.e. events defined as having
253 - SDEI events must be unmasked on the PE. I.e. the client must have called
265 - A dispatch for the same event must not be outstanding. I.e. it hasn't already
284 I.e. the caller must make sure that the requested dispatch has sufficient
291 - The call will block until the SDEI client completes the event (i.e. when the
|
| /arm-trusted-firmware-2.8.0/drivers/nxp/auth/csf_hdr_parser/ |
| A D | input_blx_ch3 | 29 # e.g FSL_UID_0=11111111
|
| A D | input_blx_ch2 | 25 # e.g FSL_UID=11111111
|
| A D | input_pbi_ch3 | 27 # e.g FSL_UID_0=11111111
|
| A D | input_pbi_ch3_2 | 27 # e.g FSL_UID_0=11111111
|
| A D | input_bl2_ch3_2 | 44 # e.g FSL_UID_0=11111111
|
| A D | input_bl2_ch3 | 44 # e.g FSL_UID_0=11111111
|
| /arm-trusted-firmware-2.8.0/lib/libfdt/ |
| A D | fdt_overlay.c | 684 const char *s, *e; in overlay_symbol_update() local
720 e = path + path_len; in overlay_symbol_update()
738 if ((e - s) > len && (memcmp(s, "/__overlay__/", len) == 0)) { in overlay_symbol_update()
741 rel_path_len = e - rel_path - 1; in overlay_symbol_update()
742 } else if ((e - s) == len in overlay_symbol_update()
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | qti-msm8916.rst | 25 therefore expects the non-secure world (e.g. Linux) to manage more hardware,
71 use e.g. `qtestsign`_::
81 of problems (e.g. using EDL).
114 …ference Manual: https://developer.qualcomm.com/download/sd410/snapdragon-410e-technical-reference-…
|
| /arm-trusted-firmware-2.8.0/docs/components/fconf/ |
| A D | fconf_properties.rst | 39 e.g. HW_CONFIG
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | porting.rst | 12 (e.g. 'plat/marvell/armada/a8k/a7040_cust').
13 - The platform name for build purposes is called ``<soc>_cust`` (e.g. ``a7040_cust``).
32 In cases where a special physical address map is needed (e.g. Special size for
49 saved in next position on flash (e.g. address 2M in SPI flash).
|
| /arm-trusted-firmware-2.8.0/drivers/nxp/crypto/caam/src/auth/ |
| A D | rsa.c | 53 ctx.pkin.e = rsa_pub_key + klen; in rsa_public_verif_sec()
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | commit-style.rst | 120 case (``this-is-kebab-case``). Components with a product name (i.e. most
121 platforms and some drivers) should use that name (e.g. ``gic600ae``,
123 component (e.g. ``marvell-comphy-3700``, ``rcar3-drivers``, ``a3720-uart``).
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | auth-framework.rst | 14 - The mechanism used to encode and transport information, e.g. DER encoded
18 - The mechanism used to verify the transported information i.e. the
30 | Code i.e. | (IO) | Port |
55 | Misc. Libs e.g. |
171 used for verifying the CoT, e.g. memory for public keys, hashes etc.
176 extract authentication parameters contained in an image, e.g. if the
204 multiple CoTs then it should be verified only once e.g. the Trusted World
214 will have been extracted from the parent image i.e. BL31 content
372 is treated as being in raw binary format e.g. boot loader images used by
379 e.g. the X.509 parsing library code in mbed TLS.
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model_el3_spm.rst | 99 - SPMC secrets (e.g. pointer authentication key when enabled)
100 - SP secrets (e.g. application keys).
169 | | spoof the origin and destination worlds (e.g. a NWd|
216 | | and another endpoint (e.g. which NWd endpoint ID |
285 | | the latter in not in a state to receive it (e.g. |
416 | | (e.g. partition message response outside of |
516 | | mitigations (e.g. speculation barriers) for the |
|
| /arm-trusted-firmware-2.8.0/tools/nxp/create_pbl/ |
| A D | README | 30 -e <Address> - [Optional] Entry Point Address
|