Björn Quentin

I think the list of items is already quite complete - if we had all of this releasing would be a breeze :) I have doubts about the first item...

The only problem currently might be that we need to store/restore the full context (not only caller saved registers) as the trap-frame since that is what the scheduler in `esp-wifi`...

I thought about this a bit more and I realized we actually added a bit more functionality over time. Maybe the functionality is already available in `riscv-rt` (need to check)...

Sure, basically it's just a timer ISR where we call https://github.com/esp-rs/esp-hal/blob/2c14e595dbc853b23a085a48aff7105eaef71652/esp-wifi/src/preempt/mod.rs#L135 There we just swap all the registers and a few CSRs ... That's all the magic :)

See #3857 See https://github.com/rust-embedded/riscv/pull/335#issuecomment-3140658097

I just tried it and both, `ps-min-modem` and `ps-max-modem` work fine for me running on ESP32-C3. (Connecting to Fritz!Box 5590 as AP) I don't think the 16MHz clock is too...

I don't think there is anything actionable right now since I am not able to reproduce this. Feel free to re-open

> Finding a solution for https://github.com/esp-rs/esp-hal/issues/1623 may fix this issue if merged into the esp-ieee802154 crate as well. Yes - I'm really interested in finding a solution for that. (You...

On ESP32 the interrupt triggered before `reg_block.cmd().modify(|_, w| w.usr().set_bit());` and before `tx.listen_eof()` - so the interrupt cleared INT_ENA, then it gets set again making the future believe the transfer is...

I agree on clearing the interrupts before preparing DMA, but regarding `reset_dma_before_usr_cmd` the TRM says