v01d commented on pull request #2302: URL: https://github.com/apache/incubator-nuttx/pull/2302#issuecomment-748087792
> BTW, to support the monolithic(profile plus l2cap/hci) bluetooth stack like zerphyr and nimBLE, the serial driver(/dev/tty*) is better interface. Here is how bluez and bluedroid work on Linux: > > 1. bluez contain profile only, and talk with kernel l2cap/hci through socket > > 2. bluedroid contain profile+l2cap+hci talk with kernel through /dev/tty* > > > It's strange and complex to support bluedroid/nimBLE through the raw/managed bluetooth socket but bypass L2CAP/HCI layer. There was already a discussion on this before and there was agreement that the way to support a BLE stack and expose a BLE controller was via networking interfaces, not custom character drivers. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
