-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Firmware] Use esp-idf instead #90
Comments
Yeah but it wont help for other architectures :/, any ideas? |
@ImUrX Indeed this will trap us into the Espressif ecosystem. What I would suggest is to put portable code into a core crate and so we can still use other kernels if we can flock to a better ecosystem |
I'm intentionally not targetting ESP-IDF. Here was the rationale:
Hopefully this explains why I am looking to build on |
@TheButlah Ah I see...I used to think that you are doubting that Espressif can provide a good ground for future either as they are based in China and US sanction can come in their way but seems like I guessed it all wrong...And the truth instead, you take this as a learning opportunity and for portability sake rather than taking it pragmatic (and maybe dramatic too). |
Quite to the contrary - this codebase heavily relies upon the incredible work done by both official espressif employees and other members of the community from esp-rs. The espressif team has done a lot to make rust work well on their chips, and are extremely responsive to the community, as well as PRs that I submit to their crates. Anyway, I'm going to mark this issue as closed, but feel free to ask any further clarifying questions. |
https://github.com/esp-rs/esp-idf-sys
The reason to use esp-idf is that we can easily port program from std, although it is only a fraction of.
The text was updated successfully, but these errors were encountered: