Skip Navigation Links | |
Exit Print View | |
man pages section 7: Device and Network Interfaces Oracle Solaris 11.1 Information Library |
- USB Multi Interface Driver
device@unit-address
The usb_mid driver is a USBA (Solaris Universal Serial Bus Architecture)-compliant nexus driver that binds to device level nodes of a composite (multi interface) device if no vendor or class-specific driver is available. The usb_mid driver creates interface nodes or interface association nodes and attempts to bind drivers to them. If no driver is found for interface association nodes, usb_ia(7D) is bound by default.
The usb_mid driver also supports a ugen(7D) interface allowing raw access to the device, for example by libusb(3LIB) applications, by passing the drivers bound to each interface. Since a libusb application might change the state of the device, you should not access the device through the child interface drivers. The usb_mid driver creates a ugen interface only if none of its children are explicitly bound to the ugen(7D) driver. Additionally, usb_mid does not create children.
64-bit x86 ELF kernel module
64-bit SPARC ELF kernel module
ugen(7D) nodes.
See attributes(5) for descriptions of the following attributes:
|
cfgadm_usb(1M), libusb(3LIB), attributes(5), usba(7D), usb_ia(7D)
Universal Serial Bus Specification 2.0—2000
Interface Association Descriptor Engineering Change Notice (ECN)—2003
Oracle Solaris Administration: Common Tasks
In addition to being logged, the following messages may appear on the system console. All messages are formatted in the following manner:
Warning: <device path> (usb_mid<instance number>): Error Message...
This device has been disconnected because a device other than the original one has been inserted. The driver informs you of this fact by displaying the name of the original device.
Same condition as described above; however in this case, the driver is unable to identify the original device with a name string.
A hotplug of the device is needed before it can be restored.
The following messages may be logged into the system log. They are formatted in the following manner:
<device path><usb_mid<instance number>): message...
No driver is available for this interface.
No driver is available for this interface.
No ugen interface is available and libusb(3LIB) cannot work with this device.