You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm currently in the process of implementing a Wi-Fi stack for the ESP32 in pure rust and I have to use raw pointer to access the registers, we found while reversing.
I wanted to ask if we could upstream our patches for the SVD, to access them through esp-hal, or should maintain them out of tree.
The text was updated successfully, but these errors were encountered:
It should be fine to upstream your findings to the PACs, we're unlikely to use them in esp-wifi (unless you figured it all out :D) but I see no harm in them being there, provided they are of decent quality.
Yeah, they're probably not of much use for esp-wifi. The thing is, that most of these names are educated guesses at best, since they have like two references and some random value is written to them. Some are more obvious, like 0x3ff73090, which is referenced in hal_mac_rx_get_last_dscr. I'd suggest putting them behind a feature flag.
@MabezDev I made a small tech demo over at: https://github.com/esp32-open-mac/esp32-wifi-hal-rs we can send, receive and change the channel. TX and RX is completely async, and we only need the blobs for RF init and some minor initialization.
Hi, I'm currently in the process of implementing a Wi-Fi stack for the ESP32 in pure rust and I have to use raw pointer to access the registers, we found while reversing.
I wanted to ask if we could upstream our patches for the SVD, to access them through
esp-hal
, or should maintain them out of tree.The text was updated successfully, but these errors were encountered: