-
Notifications
You must be signed in to change notification settings - Fork 459
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
16-bit Implementation (MSP430FR5994) #96
Comments
Hello, I have the same concern. The project eclipse tinydtls plans to use micro-ecc instead of its own ecc implementation. However, switching to micro-ecc would currently drop support to 16bit architectures. If micro-ecc would have a 16bit support, even if it was a really slow version at first, would help using it only without requiring maintaining two versions. Would you merge a 16bit support ? if yes, what do you think of the current state of #23 repository ? What additional work would you require to be done on it before merging. Thank you in advance. Regards, |
I don't mind merging 16-bit support. It would be very slow though without
any asm optimizations.
…On Wed, Mar 29, 2017 at 1:01 AM, Gaëtan Harter ***@***.***> wrote:
Hello, I have the same concern.
The project eclipse tinydtls
<https://projects.eclipse.org/projects/iot.tinydtls> plans to use
micro-ecc instead of its own ecc implementation. However, switching to
micro-ecc would currently drop support to 16bit architectures. If micro-ecc
would have a 16bit support, even if it was a really slow version at first,
would help using it only without requiring maintaining two versions.
Would you merge a 16bit support ? if yes, what do you think of the current
state of #23 <#23> repository
? What additional work would you require to be done on it before merging.
Thank you in advance.
Regards,
Gaëtan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#96 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADD2b8iLgbLWTgy0sOa6aEQpk5wTngo6ks5rqg_egaJpZM4MVmsC>
.
|
Test breaks on wsn430 boards with the node rebooting. I suspect because `micro-ecc` does not have 16b support. If that is the reason other 16bit boards may also be added there. * kmackay/micro-ecc#96
tests/pkg_micro-ecc: blacklist 16bits boards Test breaks on wsn430 boards with the node rebooting. This must come becauso `micro-ecc` does not have 16b support. I also blacklisted the other 16bits boards. * kmackay/micro-ecc#96
Test breaks on wsn430 boards with the node rebooting. I suspect because `micro-ecc` does not have 16b support. If that is the reason other 16bit boards may also be added there. * kmackay/micro-ecc#96
tests/pkg_micro-ecc: blacklist 16bits boards Test breaks on wsn430 boards with the node rebooting. This must come becauso `micro-ecc` does not have 16b support. I also blacklisted the other 16bits boards. * kmackay/micro-ecc#96
Test breaks on wsn430 boards with the node rebooting. This must come becauso `micro-ecc` does not have 16b support. I also blacklisted the other 16bits boards. * kmackay/micro-ecc#96
Test breaks on wsn430 boards with the node rebooting. This must come becauso `micro-ecc` does not have 16b support. I also blacklisted the other 16bits boards. * kmackay/micro-ecc#96
Thank you for your work on micro-ECC. I was reading in the past issues (#23) that you could possibly make a 16-bit version for the MSP430. Is this still a possibility?
Thanks!
Jason
The text was updated successfully, but these errors were encountered: