Details
- Reviewers
- None
- Group Reviewers
releng - Commits
- R9:0f9902bacb7c: releases/15.0R/relnotes: Note that usbhid(4) is the default
Diff Detail
- Repository
- R9 FreeBSD doc repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
@wulf can we add a sentence or two about any user-facing impact, config changes, etc.? For most people it will be a no-op.
What about:
- peripherals other than keyboard and mouse, like game controllers?
- special keyboard function keys (volume, brightness, etc.)
- FIDO keys handled by u2f
- Interaction with HID devices on other than USB
usbhid enables support for following devices:
- absolute mices for virtualized environments in hms(4)
- digitizers and pens in hpen(4)
- special keyboard function keys (volume, brightness, etc.) in hcons(4) and hsctrl(4)
- game controllers. XBox360 and PS4 gamepads in xb360gp(4) and ps4dshock(4) and generic devices in hgame(4)
- raw HID devices in hidraw(4)
- FIDO keys handled by u2f
Should work like before neither device name nor protocol has been changed
- Interaction with HID devices on other than USB
Not expected
Some users e.g. wsp(4) driver users may want to disable usbhid(4) for specific device due to different set of driver features. It is possible with setting of HQ_HID_IGNORE or UQ_HID_IGNORE quirks for device. See hidquirk(4) or usb_quirk(4) respectively.
Old uhid(4) features now are provided with hidraw(4) driver, Note that character device path now changed from /dev/uhid# to /dev/hidraw#. To use old path recompile kernel with option HIDRAW_MAKE_UHID_ALIAS added to kernel config. Hidraw(4) is not loaded by default. kldload hidraw.ko is required.
It also adds support for compound HID like keyboard and mice sharing the same USB interface
Looks like:
We don't have many multi-paragraph entries so this looks a bit unusual, but I think it's ok
