Changes in USB HID Device Special Files

3
Note that nnn is the three digit instance number for the device.
keyboards and mice are not differentiated in their DSF naming. Instead, the output of "ioscan -funC
hid" clearly specifies the category of HID devices associated with each DSF.
In the following output, hid_000 and hid_002 are USB keyboards.
hid_001 is a USB boot protocol mouse.
hid_003 is a USB mouse which does not support boot protocol.
hid_004 is a USB HID device other than a mouse or keyboard.
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
usbhid 2 0/0/2/0.1.0 hid CLAIMED DEVICE USB HID Kbd(0)
/dev/hid/hid_000
usbhid 3 0/0/2/0.2 hid CLAIMED DEVICE USB HID Mouse(1)
/dev/hid/hid_001
usbhid 4 0/0/2/0.3 hid CLAIMED DEVICE USB HID Kbd(2)
/dev/hid/hid_002
usbhid 5 0/0/2/1.2.0 hid CLAIMED DEVICE USB HID Pointer(3)
/dev/hid/hid_003
usbhid 6 0/0/2/1.2.1 hid CLAIMED DEVICE USB HID Other(4)
/dev/hid/hid_004
The instance numbers used in HID DSF names are unique to these devices. They are used only to
distinguish HID devices and in their device special file names. These HID instance numbers are
distinct from and may not be the same as the global HP-UX instance numbers displayed by ioscan.
For instance, in the above ioscan output, the HID instance number for the HID pointer is 3 and the
global HP-UX instance number is 5.
The new 11iv3 driver also supports the keyboard and boot protocol mouse multiplexed device
special files. Again, these DSFs allow the user to read all the input from all USB keyboards or mice
attached to the system through one file. These are the same DSFs delivered in PHKL_37814 on
11iv2 (/dev/hid/kbdmux and /dev/hid/mousemux).
To maintain compatibility with the USB-00 multiplexed files, installation of the new driver also
configures symbolic links from the old USB-00 device special files to these new multiplexed files.