-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Test TF-M config with p256-m driver #8041
Conversation
"capabilities": [ | ||
{ | ||
"mbedtls/c_condition": "defined(MBEDTLS_P256M_EXAMPLE_DRIVER_ENABLED)", | ||
"entry_points": ["import_key", "export_public_key"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't the actual list of entry points of the driver. It is, I believe, the list of entry points that are currently supported by the wrapper generator script. That's not very useful, but ok, why not have it, and complete it incrementally. But we really need to explain this, otherwise it's very misleading.
JSON doesn't have comments, but you can put one "_comment": "blah"
entry in any JSON object (i.e. a thing between braces) in a driver description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ac73ea4
to
f8dcacc
Compare
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
Those will be needed in order for the driver to implement all the PSA key management entry points (currently only implements key generation). Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Aw, CI came back red, failing with unexpected discrepancies in "driver test_tfm_config_p256m_driver_accel_ec vs reference test_tfm_config" which is exactly what matters in this PR, so does not look spurious. The CI was green 3 commits ago and I really didn't expect any of the last 3 commits to break it like this, but here we are... I'll investigate, fix, and let you know when this is ready to re-review. |
Looks like a single missing '*' from p256-m_driver_entrypoints.c, line 206 - do you want me to fix this before tomorrow? |
Ah, right, I was looking at "result analysis" while I should have been looking at all.sh components. I'm fixing this, but thanks for the offer! (Finished early yesterday due to an appointment, making up for it now.) |
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Fix pushed, should be ready for review again! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the changes!
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Description
Resolves #8006.
Note: will need rebasing if #8203 gets merged first.
Built on top ofSupersedes #8032itself built on top of #7992 (merged).One problem that was uncovered by #8032 is that the p256-m driver does not provide all entry points we'd want in order to be able to get rid of
ECP_C
andBIGNUM_C
, namely it's missing theimport_key
andexport_public_key
entry points. This PR solve that:p256-m.h
a bit.PR checklist