-
Notifications
You must be signed in to change notification settings - Fork 96
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
Update dependencies, port to portable-atomic #342
Conversation
5b06b4f
to
a1c617f
Compare
58ffbae
to
5da7d30
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.
LGTM
Given we can now relax the "target currently published esp-hal" policy (since we have a release on crates.io) is there a reason to not merge this?
I think I'd like to hear @MabezDev's opinion as this is intended to be part of the atomic emulation related changes. |
cadd6a4
to
4184579
Compare
884a4c9
to
3bea633
Compare
I went the lazy route and enabled portable-atomic on all targets. I can undo it if I shouldn't but I'm not sure right now. |
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! I think enabling by default is the way to go.
I ran my tests and everything looks good. For C6 it needs the fix in esp-rs/esp-hal#997 however |
Update esp-hal to |
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.
LGTMl, thanks!
Blocked on the next esp-hal release. The PR keeps atomic emulation stuff enabled for ESP32-S2 because the old heapless doesn't know about xtensa and so it won't enable atomic-polyfill even with the
cas
feature enabled. Other than that, RISC-V targets should now be able to compile esp-wifi with the emulation trap disabled.Closes #337
Closes #373