Bluetooth and USB

I’ve discovered that the payloads of the L2CAP packets coming in from a Bluetooth keyboard are identical to the USB messages coming in from a USB keyboard.

This means that it would be really handy to have a means of calling the USB keyboard handler with the 8-octet payload; otherwise the code will have to be duplicated.

I haven’t checked yet, but I expect the same situation will apply for Bluetooth mice.

As another consideration: the bug in reporting the length of USB interrupt IN messages is a show-stopper for any Bluetooth implementation.