v01d commented on issue #1639: URL: https://github.com/apache/incubator-nuttx/issues/1639#issuecomment-683115669
> > The management channel will be the biggest (and most important) to implement I think. > > https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/mgmt-api.txt > > Which will also cause a major re-write of apps/wireless/bluetooth/btsak btsak indeed will have to change to adapt to using both L2CAP and HCI sockets. Right now it opens an L2CAP socket but everything actually goes via ioctl()s to GATT functions which internally use L2CAP. Does adapting btsak actually make sense? Or should there be more modular applications? Having something like hcitool/gattool I think would be better. For gattool, the more immediate adaptation should be to the ATT/GATT code to convert it into a library which interfaces with L2CAP via socket. This way it would be also possible to write a standalone GATT server. For hcitool I think the HCI socket is already sufficient. ---------------------------------------------------------------- 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: [email protected]
