Lines Matching refs:to

4 This document describes how parts of the Mbed TLS functionality can be replaced at compile time to
10 …nux/POSIX-like systems and on Windows. On embedded platforms, you may need to customize some aspec…
12 …ve two mechanisms: either define `MBEDTLS_PLATFORM_XXX_MACRO` to the name of a function to call in…
24 …f the form 3.x. The interface of PSA drivers is currently still experimental and subject to change.
28 …ne), and for random generation. Calls to `psa_xxx` functions that perform cryptographic operations…
30to change, and not all operations support drivers yet. The configuration option `MBEDTLS_USE_PSA_C…
37 …DTLS_AES_ALT` for an implementation of the AES module. This is in addition to enabling `MBEDTLS_XX…
45to any C type except incomplete and array types (although they would normally be `struct` types). …
47to have a certain field, the field must have the same type and semantics as in the built-in implem…
54to move a context object in memory (except during the execution of a library function that takes t…
64 …at a pointer to a context or to a part of a context does not remain valid across function calls. A…
68 In some cases, it is possible to replace a single function or a small set of functions instead of […
72 Options to replace individual functions of cryptographic modules generally have a name obtained by …
74 …es_encrypt()` to provide an accelerated implementation of AES encryption that is compatible with t…
76 …DTLS_SHA256_PROCESS_ALT` and implement `mbedtls_internal_sha256_process()` to provide an accelerat…
78 …xt objects as the built-in implementation. If you want to use different context types, you need to
85 * During the initialization of your application, set the global variable `mbedtls_xxx` to an altern…
87 For example, to provide a custom `printf` function at run time, enable `MBEDTLS_PLATFORM_PRINTF_ALT…
89 …RM_XXX_ALT` does not change the behavior: by default, `mbedtls_xxx` points to the standard functio…