Scott Mabin

Not fixed via #24, though that definitely was a bug.

For hardware that doesn't support being in both `Input` _and_ `Output` at the same time it's currently unusable. However with eh 1.0, there is `IoPin` which is a trait for...

I missed this ping, sorry folks! This should be fixed for all single core chips, hence why @bjoernQ's ESP32-C3 based project above works. For multi core, the whole world gets...

A bit of further reading here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/spi_flash/spi_flash_concurrency.html and https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/spi_flash/index.html#implementation-details. Interrupts can fire _but_ all code **must** be in IRAM already. And like @bjoernQ already said, both cores must be stalled/spinning...

This also probably has implications for esp-wifi and its scheduler too, we don't want to starve that completely, fun problem to solve I guess :D.

With great difficulty, there is no way (in GCC or Rust) to recursively apply a linker_section attribute. This means whilst a top level function may be put inside an IRAM...

I also went with the buffer approach, I think it works quite well without duplicating code here in the cli.

@mattiasgronlund @konsulten, would you be willing to take a stab at fixing this?

Closed via https://github.com/esp-rs/esp-hal/pull/1445, thanks again @konsulten!

I'm wondering if in a congested network esp-wifi can somehow miss/drop packets - it seems on a quiet network (mine & @bjoernQ) it seems to work quite well but in...