QNX Technical Articles
QNX® 4.25 RTOS USB 2.0 Drivers (Beta) Release Notes
Date of this edition: October 07, 2005
Host OS: QNX® 4.25 base or any patch level
Contents
Archive contents
The USB 2.0 driver archive for QNX 4 contains:
| File | Description |
|---|---|
| /bin/devu-kbd | New USB keyboard class driver |
| /bin/devu-mouse | New USB mouse class driver |
| /bin/devu-prn | New USB printer class driver |
| /bin/io-usb | New USB stack; includes internal support for OHCI, UHCI and EHCI (USB 2.0) chipsets. |
| /bin/usb | New USB status utility; displays USB device information. |
| /bin/Fsys.umass | New USB mass storage class driver (USB flash keys, USB HDD, etc...) |
Fixed issues
- devu-mouse:
- added support for 3 button mice
- io-usb:
- fixed a problem with command line argument parsing (passing a -n option after a -d option would not take effect)
- fixed a problem with the command line hc processing where only the first hcs" was started
- fixed a problem with the command line hc processing when pindex was not specified
- fixed a problem with shared interrupts where the interrupt mask reference count could become invalid
- fixed a timing related problem with shared interrupts for chipset initialization / interrupt attaches
- Fsys.umass:
- fixed a problem with Y-E data floppy drive detection
- added a new command line option, dwait, that configures the device enumeration interval. The following command line will wait up to 60 seconds for 2 mass storage devices to enumerate:
Fsys.umass umass dwait=60:2
Known issues
- Isochronous transfers are currently not supported on USB 2.0 devices. They are supported on USB 1.1 devices only.
- When using a USB 2.0 PCI card, do not run show_pci with a -v option as you can experience a board lock-up since it disables the devices to determine aperture sizes. Running show_pci without that option is fine.
- The Fsys.umass (USB Mass Storage driver) doesn't support plug and play. This means that the
device must be already connected when the driver is started. Before disconnecting the device,
the driver should be terminated via the following method:
- Unmount all filesystems:
# umount /mountpoints
- In the case of a raw device:
# rm /dev/device_name
- In the case of a partitioned device:
# umount /dev/device_name # rm /dev/device_name
- Unmount all filesystems:
Online documentation
This QNX4 USB 2.0 driver package doesn't update the online documentation. However, you'll find the drivers' latest options in their respective use messages.
For example:
use io-usb
Technical support
If you have any questions, comments, or problems with a QNX product, we recommend that you use our support forums available from our news server, news://nntp.qnx.com
For this release, use: qdn.private.beta.qnx425
Since developers and support staff frequent our newsgroups, you should find them to be your best avenue of support for solving problems.