The following USB driver enhancements are included.
USB CDC ACM device support – The acm driver can work with devices that are compliant with the USB Communication Class Device specification's Abstract Control Model and some PCMCIA cards that have modem capabilities.
The pppd daemon can access these devices through the /dev/term/[0~9]* entries. For more information, see pppd(1M).
For more information, see usbsacm(7D).
Generic USB driver – USB devices can now be accessed and manipulated by applications using standard UNIX® read(2) and write(2) system calls, and without writing a special kernel driver. Additional features include:
Applications have access to raw device data and device status.
The driver supports control, bulk, and interrupt (in and out) transfers.
Starting in the Solaris 10 6/06 release, the ugen driver no longer needs to bind explicitly to a device. By default, usb_mid binds to devices that lack a class driver and exports a ugen interface that works with libusb. For example, you can plug in a USB camera that is not a mass-storage device and use a libusb application to access it. In addition, both scsa2usb and usbprn drivers export ugen interfaces and libusb applications can be used on these classes of devices directly.
For more information, refer to ugen(7D).
USB serial driver support
Digi Edgeport USB support – The Edgeport USB driver only works with Edgeport devices and not with other USB serial devices.
New devices are accessed as /dev/term/[0-9]* and /dev/cua/[0-9]*.
USB serial ports are usable as any other serial port would be, except that they cannot serve as a local serial console. The fact that their data is run through a USB port is transparent to the user.
For more information, see usbser_edge(7D), or go to the following sites:
Keyspan – The Keyspan USB serial driver only works with Keyspan devices, which currently supports the USA-19HS and USA-49WLC models.
For more information, see usbsksp(7D).
Prolific – The Prolific USB serial driver only works with devices based on the PL2303 chipset.
For more information, see usbsprl(7D).
For more information about the USB to serial devices support, go to the following site:
Documentation and binary support for user-written kernel and userland drivers – For up-to-date information on USB driver development, go to:
Features of the EHCI driver include:
Complies with enhanced host controller interface that supports USB 2.0.
Supports high-speed control, bulk, interrupt, and isochronous transfers.
The USB 2.0 chip has one EHCI controller and one or more OHCI or UHCI controllers.
A USB 1.1 device is dynamically assigned to the OHCI or UHCI controller when it is plugged in. A USB 2.0 device is dynamically assigned to the EHCI controller when it is plugged in.
Use the prtconf command output to identify whether your system supports USB 1.1 or USB 2.0 devices. For example:
# prtconf -D | egrep "ehci|ohci|uhci" |
If your prtconf output identifies an EHCI controller, your system supports USB 2.0 devices.
If your prtconf output identifies an OHCI or UHCI controller, your system supports USB 1.1 devices.