Dario Nieuwenhuis

Fixed in #726

Fixed in #719. Users are no longer supposed to set `0.0.0.0/0` as an IP address, instead they should set no IP addr at all. #719 makes it possible in nostd.

`embassy-time` is now executor-agnostic by default. You can enable an executor agnostic queue with the `embassy-time/generic-queue` feature, or you can enable the embassy-executor-integrated one with `embassy-executor/integrated-timers`.

Thanks! Closed it will be then.

https://github.com/embassy-rs/embassy/pull/1125 removed `atomic_polyfill` for uses that were only load/store (no CAS). The esp32c3 hardware (`riscv32imc`) is capable of doing that. It is (IMO) a rust bug that load/store atomics aren't...

basic work done in https://github.com/embassy-rs/embassy/pull/2469 issues for follow-up work: https://github.com/embassy-rs/embassy/issues/2653 https://github.com/embassy-rs/embassy/issues/2654 https://github.com/embassy-rs/embassy/issues/2655

Going to close this since all these SPI bugs are fixed now AFAIK. If the issue persists please ping and I'll reopen.

No, removing public API is always a breaking change, regardless of whether it was marked as deprecated or not.

I don't think this is a good idea. `SpiBus` and `SpiDevice`'s `write()` methods have very different meaning, even if their signature is the same. - `SpiBus::write()`: clock out the bytes,...

> It would be useful to have the ability to use a bus as device. If the device has a CS pin, but it's permanent active by direct connection to...