88c8623ced
esp_openeth_initialize() (arch/xtensa/src/common/espressif/esp_openeth.c) attaches the MAC interrupt with esp_setup_irq() but never calls up_enable_irq(OPENETH_IRQ_MAC), unlike every other Espressif driver in this tree. Left masked, openeth_isr_handler() never runs and received frames are only picked up when the netdev work thread happens to run for some other reason (a transmit). A guest can therefore send but effectively not receive: ping still works because each request is itself a transmit, while a socket blocked in recvfrom() waits on a wake-up that never comes. Confirmed with a GDB breakpoint counter on openeth_isr_handler(): zero hits before the fix, dozens after, under QEMU's esp32s3 machine (the open_eth NIC it emulates). With the interrupt enabled, TCP retransmits over a fixed test window dropped from 86 to 4. Separately, openeth_ifdown() calls openeth_enable() right under a comment that says "Disable TX and RX" -- it should call openeth_disable(), which is what actually disables the two DMA descriptor rings. Fixed alongside since it's the same function and the same class of mistake. Board-independent (arch/xtensa/src/common/espressif), not specific to any one esp32s3 board; open_eth itself only exists as a QEMU peripheral, so there's no real-hardware regression risk from either change. Signed-off-by: Felipe Moura <moura.fmo@gmail.com> Assisted-by: Claude:claude-sonnet-5 |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.