UHID(4) | Device Drivers Manual | UHID(4) |
uhid
—
uhid* at uhidev? reportid ? flags N
uhid
driver provides support for all HID (Human
Interface Device) interfaces in USB devices that do not have a special driver.
Normally the uhid
driver is used when no
other HID driver attaches to a device. If “flags 1” is
specified, the uhid
driver will instead attach with
a very high priority and always be used. Together with the
vendor
and product
locators
on the uhidev(4) driver this
can be used to force the uhid
driver to be used for
a certain device.
The device handles the following ioctl(2) calls:
USB_GET_REPORT_ID
(int)
USB_GET_REPORT_DESC
(struct usb_ctl_report_desc)
struct usb_ctl_report_desc { int ucrd_size; u_char ucrd_data[1024]; /* filled data size will vary */ };
USB_SET_IMMED
(int)
USB_GET_REPORT
(struct usb_ctl_report)
report
field indicates which report is
requested. It should be UHID_INPUT_REPORT
,
UHID_OUTPUT_REPORT
, or
UHID_FEATURE_REPORT
. This call may fail if the
device does not support this feature.
struct usb_ctl_report { int ucr_report; u_char ucr_data[1024]; /* used data size will vary */ };
USB_SET_REPORT
(struct usb_ctl_report)
report
field
indicates which report is to be set. It should be
UHID_INPUT_REPORT
,
UHID_OUTPUT_REPORT
, or
UHID_FEATURE_REPORT
. This call may fail if the
device does not support this feature.USB_GET_DEVICE_DESC
(usb_device_descriptor_t)
USB_GET_DEVICEINFO
(struct usb_device_info)
USB_GET_STRING_DESC
(struct usb_string_desc)
struct usb_string_desc { int usd_string_index; int usd_language_id; usb_string_descriptor_t usd_desc; };
Use read(2) to get data from the device. Data should be read in chunks of the size prescribed by the report descriptor.
Use write(2) send data to the device. Data should be written in chunks of the size prescribed by the report descriptor.
uhid
driver appeared in NetBSD
1.4. Support for the USB_GET_DEVICEINFO
and
USB_GET_STRING_DESC
ioctls appeared in
NetBSD 2.0.
May 14, 2012 | NetBSD 9.4 |