anchao commented on PR #20686: URL: https://github.com/apache/nuttx/pull/20686#issuecomment-6376249772
By the way, there's an interesting comparison worth noting. Not long ago, someone proposed integrating lwIP as an auxiliary TCP/IP stack in NuttX (PR #20159 [https://github.com/apache/nuttx/pull/20159](https://github.com/apache/nuttx/pull/20159) / #20160). It was ultimately rejected, and rightfully so — NuttX's native TCP/IP stack is already mature and performant; when tuned properly, it matches or exceeds lwIP. In that case, enhancing the native solution is clearly the right choice over importing a third-party one. Bluetooth on NuttX is the mirror image of this situation. The native BT capability has been so lacking that the community has repeatedly resorted to third-party imports like NimBLE just to fill the gap. For an RTOS to depend on fragmented third-party solutions for something as fundamental as Bluetooth is, frankly, not a healthy state. zblue is an attempt to fix exactly this — to provide a single, comprehensive, well-maintained Bluetooth stack that can eventually replace both the legacy `WIRELESS_BLUETOOTH` and the third-party `NIMBLE`. It's not "another option" — it's the consolidation path. So I'd argue that giving it a clean, direct `CONFIG_BT` entry point, rather than tucking it behind an abstraction layer built for a fragmentation problem we're actively trying to solve, is the right call. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
