bunnie 6f86aee991 give loopback its own rx buffer ... instead of sharing the wifi buffer loopback has its own buffer. this eliminates a race condition that happens whenever an Rx happens to happen on the wifi interface while there's loopback traffic in progress. also, i see a lot of opportunities to optimize the net stack now that i have tweaked this path; it might be interesting to break the receive interrupt out directly into the COM crate instead of passing it through LLIO then NET then COM and having COM drain the RX buffer immediately into a local "infinite" sized queue. The llio->net->com loop exists because the interrupt handler for all the i/o is shared within one hardware block, but maybe i can create an additional interrupt responder for the com interface just to optimize things a bit in a future SOC update. Alternatively, I could move all the interrupts into COM and not have them resident in LLIO. This would optimize for COM latency at the expence of I2C latency, but that's probably OK because I2C is much less latency sensitive (i2c and com interrupt, as mentioned above, share the same hardware block for external pin-based interrupts).		2022-08-05 15:12:57 +08:00
..
src	give loopback its own rx buffer	2022-08-05 15:12:57 +08:00
Cargo.toml	rework semver returns and fix flash verify bugs in COM	2022-07-11 04:07:00 +08:00