-
Notifications
You must be signed in to change notification settings - Fork 54
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
Fix little-endian Microblaze does not work when MBEDTLS_HAVE_ASM is defined #38
Conversation
@alpsayin please open a corresponding Zephyr PR that updates the manifest to this PR. |
@alpsayin Can you please update the commit message to say "(Cherry-picked from )" instead? Easier to find all downstream patches if you can search for that line. |
Sure thing, aaand done! I only used "adopted" to imply it wasn't a direct cherry-pick, but I now realise the value. |
No, actually it still is valuable @alpsayin, because then we get the reference with the Git cmd line as well. Please do |
@carlescufi He did, it's good now. |
To be clear, I didn't do |
It's only the message, and it looks identical, so no problem. |
…TLS_HAVE_ASM is defined. Signed-off-by: Kazuyuki Kimura <[email protected]> Signed-off-by: Dave Rodgman <[email protected]> (cherry picked from commit b88dbdd) Signed-off-by: Alp Sayin <[email protected]>
Since the bump to v3.2 I've cherry-picked the actual commit as-is, which should make life easier when it's time to bump to v3.3. |
Depends on zephyrproject-rtos/zephyr#53899 because this is based on mbedTLS v3.2 which needs TFM v1.7 |
@alpsayin Zephyr now uses mbedtls 3.3.0, so this change is now included. I will therefore close this PR. |
Description
MbedTLS multiplication assembly sources for big numbers not accounting for little endian. Causing zephyr mbedtls unit test to fail when executing mbedtls self-test
MPI test #1 (mul_mpi)
.Cherry-picked from Mbed-TLS/mbedtls@b88dbdd
Depends on zephyrproject-rtos/zephyr#53899 because this is based on mbedTLS v3.2 which needs TFM v1.7
Status
READY
Requires Backporting
No, because microblaze support isn't there yet. Therefore this can be considered as part of a new feature.
Additional comments
Issue was first reported in upstream mbedtls here:
Mbed-TLS/mbedtls#2020
And the fix was implemented in upstream mbedtls here:
Mbed-TLS/mbedtls#4686
Todos
Steps to test or reproduce
compiler/zephyr-sdk: microblaze-gcc from topic-microblaze branch of sdk-ng which based on 0.15
Get the toolchain from here: https://github.com/zephyrproject-rtos/sdk-ng/suites/9030507693/artifacts/417018783
zephyr version:
v3.2.0
Get the microblaze port here (rebased on
v3.2.0-branch
): https://github.com/alpsayin/zephyr/tree/microblaze_v3.2.0_publiczephyr version:
main
Get the microblaze port here (rebased on
main
): https://github.com/alpsayin/zephyr/tree/microblaze_publiccommand:
./scripts/twister -v -p qemu_microblaze -O /scratch/esnap_$USER/twister_out -T tests/crypto/mbedtls