Thank you Charles. I'm sorry I missed the distinction you've outlined. Hopefully this will help the next person who thinks the libhid is the place to go.
Cheers, On Fri, Feb 10, 2017 at 9:48 AM, Charles Lepple <clep...@ghz.cc> wrote: > On Feb 10, 2017, at 8:48 AM, Chip Wachob wrote: > > > Hopefully the Bluetooth group doesn't send me back to HID. > > > The distinction is that this particular libhid was designed to interface > with USB HID devices (uninterruptible power supplies, servo control boards, > etc.) that do not fit into the traditional input peripheral model (yet > still use HID over USB). > > Bluetooth adopted the HID model for traditional input devices (keyboard, > mouse, headsets with buttons, etc.), and the fact that many Bluetooth > adapters use USB is merely coincidence. In that case, USB is one of the > transport layers for Bluetooth, and Bluetooth is the transport layer for > HID. Oversimplified for sure, but contrast with libhid, which was using USB > as the transport layer for non-keyboard/mouse HID, and has no connection to > any of the Bluetooth protocol stack (including SDP). > > There seem to be a number of step-by-step guides if you do a web search > for "emulate Bluetooth Linux". > > -- > - Charles Lepple > https://ghz.cc/charles/ > > >
_______________________________________________ libhid-discuss mailing list libhid-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/libhid-discuss http://libhid.alioth.debian.org/