tmedicci commented on issue #15347: URL: https://github.com/apache/nuttx/issues/15347#issuecomment-2569393605
Hi @Laczen, Usually, NuttX drivers are split into a lower-half and upper-half, as described [here](https://nuttx.apache.org/docs/latest/components/drivers/index.html#lower-half-and-upper-half). Network drivers, however, doesn't seem to follow the same path. If you check about `spirit_netdev.c`'s [`spirit_netdev_initialize`](https://github.com/apache/incubator-nuttx/blob/286d37026c3b7f3923a45d7c114200a6546ba030/drivers/wireless/spirit/drivers/spirit_netdev.c#L2610) function is being called directly from the board-level (from `nuttx/boards/arm/stm32l4/b-l475e-iot01a/src/stm32_spirit.c`, for instance). That being said, as ESPnow is specific for Espressif devices, I think you should implement it on `nuttx/arch/xtensa/src/common/espressif` (once it can be used by more Espressif's SocS) in a similar way it's done for Wi-Fi (check [`esp32s3_net_initialize`](https://github.com/apache/incubator-nuttx/blob/93086756865486380ae8e059592b23282b0ac377/arch/xtensa/src/esp32s3/esp32s3_wlan.c#L1458) function, for instance). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
