anchao commented on PR #20686: URL: https://github.com/apache/nuttx/pull/20686#issuecomment-6385593448
> @anchao > > I think that is our main point of divergence: I think ZBlue should be an option to allow others BT/BLE stack be used in the future, you think that ZBlue should become the NuttX default BT/BLE stack. > > If you use CONFIG_BT_ZBLUE_HCI/L2CAP/GATT, etc, everybody will understand what it means, but selecting CONFIG_BT_HCI/etc to ZBLUE means we are giving it higher privilege (I think NimBLE and other should have the same opportunity to evolve). NimBLE for instance is actively maintained and was certified on Espressif chips: https://www.espressif.com/en/news/BLE_5.0_Certification > > So, my point is: I am fine to let ZBlue in, but I'm not fine to let it to become the standard/official NuttX BT/BLE stack. @acassis I think we've reached an impasse here. I'm unable to convince you, and I'm not willing to restructure the Kconfig naming in the way you're asking for. So I'm going to withdraw this PR for now. Thanks for the discussion. -- 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]
