ivmarkov

Shall we instead expose the `nvs_handle_t` member, so that you can call any unsafe APIs on it, if you wish to?

I'm closing this because the `next` branch now has a `RawHandle` trait, which is implemented everywhere where it makes sense, including `EspNetif`. `next` to be released soon.

It is simply **not possible** to block using FreeRtos APIs for less than one tick (one tick = 10ms by default; can be lowered to 1ms, but not less). So...

Are we fixing the non-compliance with `embedded-hal`, or are we trying to solve your one-wire problem? >> Ran into this trying to bitbang a 1-Wire interface, and still can't seem...

Don't get me wrong - let's see if you can address your concrete problem by using `Ets` first. As for fixing the `FreeRtos` us delay.. none of the suggested methods...

The changes to `esp-idf-svc` look quite OK, thank you. Accidentally however, I found [this](https://github.com/rust-lang/rust-bindgen/issues/758) this morning. Sorry, I know this is late and we should have discussed it before I...

> The changes to `esp-idf-svc` look quite OK, thank you. Accidentally however, I found [this](https://github.com/rust-lang/rust-bindgen/issues/758) this morning. Sorry, I know this is late and we should have discussed it before...

OK so here's my take on this (to be discussed on the upcoming esp-rs meeting this Tuesday): I think we are chasing diminishing results. # Constified "enums" - These are...

> > `Default::default` for this and that > > Regarding `Default` I think the best bet would be to not implement the zeroing `Default` for any types since it's not...

@MabezDev I think you are following the development of RMT and mcpwm. Would you like to review this and #93 and merge when you think this stuff is in a...