-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
interrupt: Support Xtensa #86
Conversation
6c5bf77
to
a2efd4e
Compare
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.
Just swinging by to say thanks for this, will be very useful for the esp-rs community! The implementation looks good to me also, we have a similar implementation in esp-hal, just with a different level (to allow debug interrupts to occur).
I noticed some TODO's in the CI, if you are having issues setting up the toolchain let me know. We also have github action for installing the toolchain in CI if that's useful: https://github.com/esp-rs/xtensa-toolchain
a7fac8f
to
c584a97
Compare
TODO in CI is about tests on CI (using a simulator). I mainly use QEMU and semihosting crate to test no-std targets, so I tried to do the same with Xtensa, but the compiler didn't seem to recognize the Tests passed except for a few tests that ran into compiler bugs (?).
(These may be known problems.) |
Published in 1.3.0. |
This adds
portable_atomic_unsafe_assume_single_core
support for Xtensa targets without atomic CAS.