Scott Mabin
Scott Mabin
Related to #1973, we're leaning towards using MCUBOOT, but we need to explore if this is viable before we settle on it. The most important thing we need to know...
## Thank you for your contribution! We appreciate the time and effort you've put into this pull request. To help us review it efficiently, please ensure you've gone through the...
I think it might just be cleaner to have `new` always take a config, users can always just pass `Default::default()`. Related to #2010 and #2321
## Motivations We should offer some way to validate the user provided options make sense, this may include: * [ ] Ensuring provided integers are between upper and lower ranges...
Whilst we don't intend to do a full chip bring-up until the mass production version is released, we would like to get a minimal chip bring-up to aid future developments....
If we end up doing #2299 many features of esp-wifi will move away, but many of the remaining ones we should remove and enable by default, like we did for...
Some drivers have this module public, some don't. Imo now `async` is enabled by default, we should make these modules private and reexport the relevant public bits.
Feels a bit odd that it's included in esp-wifi itself, given that our/other BLE stack is separate. I think we should either extract it, or consider another blocking stack to...
It's hard to tell what should and what shouldn't be exposed in the rtc_cntl module with tonnes of cfgs everywhere. We should split this up with a top level public...
As per the API-GUIDELINES, we should already be doing this. Once #2187 is merged we could also look at automatically deiniting if it's not being used.