Lines Matching +full:- +full:m

5 …osed, work-in-progress driver system. The [PSA Driver Interface](https://github.com/Mbed-TLS/mbedt…
6 …-TLS/mbedtls/blob/development/docs/proposed/psa-driver-developer-guide.md) Guide describes the del…
9 [Background on how Mbed TLS calls drivers](#background-on-how-mbed-tls-calls-drivers)\
10 [Process for Entry Points where auto-generation is implemented](#process-for-entry-points-where-aut…
11 …ocess for Entry Points where auto-generation is not implemented](#process-for-entry-points-where-a…
12 …tware accelerator alongside Mbed TLS](#example-manually-integrating-a-software-accelerator-alongsi…
16 …-party drivers. Operations that are completed within one step (one function call), such as verifyi…
19 …ivers can also be pure software implementations that are distributed as plug-ins to a PSA Cryptogr…
20 …y location](https://github.com/Mbed-TLS/mbedtls/blob/development/docs/proposed/psa-driver-interfac…
22 …-part of a multi-part operation), the library calls the corresponding function in the driver wrapp…
24 The long-term goal is for the driver dispatch layer to be auto-generated using a JSON driver descri…
25 …-generation logic has already been implemented. When accelerating these operations, the instructio…
27 …-generation of the driver wrapper is supported for the operation entry points specified in the tab…
30 |---------------------|---------------------|
37 ### Process for Entry Points where auto-generation is implemented
39 …-TLS/mbedtls/blob/development/docs/proposed/psa-driver-developer-guide.md) and [integration](https…
42  - A driver description file (in JSON format).
43 …- C header files defining the types required by the driver description. The names of these header …
44 …- An object file compiled for the target platform defining the functions required by the driver de…
46 …-TLS/mbedtls/blob/development/scripts/data_files/driver_jsons/mbedtls_test_transparent_driver.json…
48 ### Process for Entry Points where auto-generation is not implemented
50 …r*. Steps 4, 5, and 6 must be done *for each single-part operation* or *for each sub-part of a mul…
77 …driver wrapper functions. For the entry points that have driver wrapper auto-generation implemente…
127 … This is the preferred option when your project uses Mbed TLS mostly out-of-the-box without signif…
130     make CFLAGS="-DDRIVER_PREFIX_ENABLED"
135     CFLAGS="-DDRIVER_PREFIX_ENABLED" cmake path/to/source
141 …-m](https://github.com/mpg/p256-m) is a minimalistic implementation of ECDH and ECDSA on the NIST …
143 … build system includes the instructions needed to build p256-m. To build with and use p256-m, set …
149 …-in implementation of ECC algorithms, which includes more features than p256-m. Refer to the docum…
151 The driver prefix for p256-m is `P256`/`p256`.
152 The p256-m driver implements the following entry points: `"import_key"`, `"export_public_key"`, `"g…
153 …cessary for a sign-and-hash algorithm. The core still implements these functions by doing the hash…
154 …-m; converting between PSA and p256-m argument formats and performing sanity checks. If the driver…
156 …-m only supports non-deterministic ECDSA using keys based on NIST P256; these constraints are enfo…
180 …his, p256-m is now ready to use alongside Mbed TLS as a software accelerator. If `MBEDTLS_PSA_P256…