-
Notifications
You must be signed in to change notification settings - Fork 3k
Add a new top level config.h for mbedtls #2716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@sbutcher-arm @yanesca |
7f64d2b
to
8094dc8
Compare
@0xc0170 we should have a hal and device attribute for |
8094dc8
to
7e814a5
Compare
bb89793
to
fe42054
Compare
fe42054
to
c1d5ee9
Compare
This PR is dependent on #2765 |
c1d5ee9
to
ae6383f
Compare
+1 |
Code looks good. TRNG should land soon, this will be rebased, and will be ready for integration |
Looks good to me. |
@andresag01 Looks like a conflict needs to be resolved and then CI run |
ae6383f
to
21a7b1d
Compare
retest uvisor |
/morph test |
retest uvisor |
1 similar comment
retest uvisor |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 965 All builds and test passed! |
Description
This PR enables the possibility to use a new configuration file
config-no-entropy.h
recently added to mbed TLS (Mbed-TLS/mbedtls#615) that allows the subset of the library to be used when the target MCU does not implement an entropy source. To do so, aENTROPY_SOURCE
value is added to the targets that have entropy source in thetarget.json
file. Also, the mbed TLS importer script is modified to copy aconfig-no-entropy.h
into the mbedtls include folder.I have assumed that all targets that define
MBEDTLS_ENTROPY_HARDWARE_ALT
implement an entropy source, so I have addedENTROPY_SOURCE
to all of these.Status
IN DEVELOPMENT
Migrations
NO
Related PRs
This is related to the PR Mbed-TLS/mbedtls#615 in mbed TLS.
Steps to test or reproduce