Editing Human interface device (section)

=== Components of the HID protocol ===
In the HID protocol, there are 2 entities: the "host" and the "device". The device is the entity that directly interacts with a human, such as a keyboard or mouse. The host communicates with the device and receives input data from the device on actions performed by the human. Output data flows from the host to the device and then to the human.  The most common example of a host is a [[Personal computer|PC]] but some [[Mobile phone|cell phones]] and [[Personal digital assistant|PDAs]] also can be hosts.

The HID protocol makes implementation of devices very simple. Devices define their data packets and then present a "HID descriptor" to the host. The HID descriptor is a hard coded array of bytes that describes the device's data packets. This includes: how many packets the device supports, the size of the packets, and the purpose of each byte and bit in the packet.  For example, a keyboard with a calculator program button can tell the host that the button's pressed/released state is stored as the 2nd bit in the 6th byte in data packet number 4 (note: these locations are only illustrative and are device-specific). The device typically stores the HID descriptor in ROM and does not need to intrinsically understand or parse the HID descriptor. Some mouse and keyboard hardware in the market today is implemented using only an 8-bit [[ATtiny microcontroller comparison chart|CPU]].

The host is expected to be a more complex entity than the device. The host needs to retrieve the HID descriptor from the device and parse it before it can fully communicate with the device. Parsing the HID descriptor can be complicated.  Multiple operating systems were known to have shipped bugs in the [[device driver]]s responsible for parsing the HID descriptors years after the device drivers were originally released to the public. However, this complexity is the reason why rapid innovation with HID devices is possible.

The above mechanism describes what is known as HID "report protocol". Because it was understood that not all hosts would be capable of parsing HID descriptors, HID also defines "boot protocol". In boot protocol, only specific devices are supported with only specific features because fixed data packet formats are used. The HID descriptor is not used in this mode so innovation is limited. However, the benefit is that minimal functionality is still possible on hosts that otherwise would be unable to support HID. The only devices supported in boot protocol are
* Keyboard – Any of the first 256 key codes ("Usages") defined in the HID Usage Tables, Usage Page 7 can be reported by a keyboard using the boot protocol, but most systems only handle a subset of these keys.  Most systems support all 104 keys on the [[IBM PC keyboard|IBM AT-101]] layout, plus the three extra keys designed for [[Windows 95|Microsoft Windows 95]] (the left and right [[Windows key]], and the [[Menu key]]).  Many systems also support additional keys on basic western European 105-, Korean 106-, Brazilian ABNT 107- and Japanese DOS/V 109-key layouts. Buttons, knobs and keys that are not reported on Usage Page 7 are not available.  For example, a particular US keyboard's QWERTY keys will function but the Calculator and Logoff keys will not because they are defined on Usage Page 12 and cannot be reported in boot protocol.
* Mouse – Only the X-axis, Y-axis, and the first 3 buttons will be available.  Any additional features on the mouse will not function.
One common usage of boot mode is during the first moments of a computer's boot up sequence.  Directly configuring a computer's [[BIOS]] is often done using only boot mode.
Sometimes a message will appear informing the user that the device has installed the correct driver and is now usable.