![[LWN Logo]](/images/lwn.banner.gif)
From: Brad.Hards@dao.defence.gov.au
To: linux-usb@suse.com
Date: Mon, 13 Dec 1999 11:58:01 +1000
Subject: [linux-usb] SEC: UNCLASSIFIED:-HOWTO version 0.9
This is the latest version of the HOWTO USB for Linux. Like a lot of other
people, I have had problems keeping up with URBisation, which is one of the
reasons why this release of the HOWTO has been delayed (along with finishing off
my Masters degree, changing jobs and some contract USB work...).
The (fairly arbitrary) approach I eventually decided on was to use the current
kernel configuration, plus the current pre-patch, but no other patches. My
reasoning is that this is the sort of capability and level of effort that most
of the USB testers have. While some people will be willing to put in additional
patches, they probably won't need the HOWTO to tell them what to do.
Enough philosophy: this version fixes up a number of problems. There is at least
one broken link. Finding it (and telling me where it changed to) is left as an
exercise for the reader. I have finally relented and included mass storage
device instructions, even though I am not entirely comfortable with the concept
(fix the Zip drive Paulus...). The DC-2xx stuff will hopefully go into the next
version. Please let me know if I have stuffed any of this up - even a single
typo.
Brad
P.S. A huge thankyou to everyone who is working on this stuff. It _is_ worth it,
even the little conflicts we sometimes share, for the end goal, which is (to my
mind) "A faster, more reliable, better documented and more complete USB
capability than anyone else".
--------------------------------------
How to get USB devices working under Linux
Brad Hards
$Revision: 0.9.0 $
This document is an early draft of a step-by-step guide to getting USB
devices working on a Linux system
This document is matched to Linux kernel revision 2.3.32-pre2. Some of
this stuff is outright guesswork, especially the lesser known and more
expensive devices, which I don't have.
_________________________________________________________________
Basic USB Configuration
You need a late version kernel. Kernel versions 2.2.7 and later
contain the USB code. You should, in an ideal world, be running the
current 2.3.x kernel, ideally with any pre-patches for the next
kernel. It is possible to use the 2.3.x USB code with a 2.2.x kernel -
see later in this document for details. USB code is in fairly early
development, so the changes between each version (and the bugs) tend
to change fairly fast. Support on the mailing list for anything except
the lastest version is scant at best.
The mailing list is <[1]linux-usb@suse.com>. To subscribe, send a mail
message to <[2]majordomo@suse.com> with content of subscribe
linux-usb. If you want to stop getting mailing list content, send a
mail message to <[3]majordomo@suse.com> with content of unsubscribe
linux-usb.
You need to configure USB into your kernel. Use of make menuconfig is
recommended. Under Support for USB , you need to select Support for
USB. You also need to select one of UHCI (intel PIIX4 and others)
support, OHCI (Compaq and some others) support or OHCI-HCD (other OHCI
opt. Virt. Root Hub) support. Use of more than one of UHCI, OHCI, and
OHCI-HCD at the same time is not expected to fully work (UHCI might
work). Which one you select is dependent on what kind of motherboard
or adapter you have. Intel and Via motherboards, and Via based
adapters are UHCI. Ali chipsets, Compaq and NEC motherboards, iMacs
and any adapter using Opti chips (just about all of them) are OHCI,
and you can use OHCI or OHCI-HCD, at your option. If you do not know
what kind of controller to choose, check your motherboard
documentation. You can also look at /proc/pci for a hint - if the USB
entry is of the form 0xHHHH, where HHHH are hex digits (e.g. something
like I/O at 0xe400), then it is UHCI. If it is of the form 32 bit
memory at 0xHH000000, where HH are hex digits (e.g. something like 32
bit memory at 0xee000000), then it is OHCI. Failing that, just try
one.
You also need to select whichever devices you want to use, for example
USB mouse support for a USB mouse, USB HP scanner support for certain
HP scanners, USB keyboard support for a USB keyboard, USB Audio
support for USB speakers, USB Communications Device Class (ACM)
support for a POTS or ISDN modem, USB Printer support for a USB
printer, USB Belkin and Peracom serial port support for some serial
port adapters, USB CPiA Camera support for cameras based on the Vision
CPiA chipset, USB Kodak DC-2xx Camera Support for downloading images
from Kodak's DC-200 series cameras, USB SCSI Support for mass storage
devices, EZUSB Firmware downloader for downloading into an Anchor
Chips USB microcontroller kit, and USS720 parport driver for certain
parallel port adapters. You should be able to use modules, kernel
only, or split modules and kernel code.
USB hubs are automatically supported. Some devices may stop and start
working between kernel versions. Remember that you are using
experimental code. Devices not listed in this document are not working
at the time of writing, although developers are always welcome to
contribute to the current codebase.
If you want to use a stable kernel (2.2.x), you can replace the code
in the drivers/usb directory with the code from a developmental kernel
(2.3.x). Then apply the latest version of the backport patch from
[4]http://www.suse.cz/development/usb-backport/
Rebuild the kernel and the modules (if you configured to build as
modules), and install the new kernel and the new modules. Reboot the
system.
If you are using modules, you need to load the following modules:
* usbcore.o
* usb-uhci.o, usb-ohci.o or usb-ohci-hcd.o
and any driver modules, such as mouse.o or keyboard.o,
Inspect the kernel logs. You should see lines like the following
(assuming use of UHCI and an external hub)
.......
Jul 19 20:46:02 rachel kernel: USB HID boot protocol mouse registered.
.......
Jul 19 20:46:02 rachel kernel: uhci_control_thread at c01b8c5c
Jul 19 20:46:02 rachel kernel: New bus registered
Jul 19 20:46:02 rachel kernel: USB hub driver registered
Jul 19 20:46:02 rachel kernel: uhci_connect_change: called for 0
.......
Jul 19 20:46:02 rachel kernel: USB hub found
Jul 19 20:46:02 rachel kernel: hub: 4-ports detected
Jul 19 20:46:02 rachel kernel: hub: individual port power switching
Jul 19 20:46:02 rachel kernel: hub: standalone hub
Jul 19 20:46:02 rachel kernel: hub: individual port over current protection
Jul 19 20:46:02 rachel kernel: hub: power on to power good time: 100ms
Jul 19 20:46:02 rachel kernel: hub: hub controller current requirement: 100mA
Jul 19 20:46:02 rachel kernel: hub: port 1 is removable
Jul 19 20:46:02 rachel kernel: hub: port 2 is removable
Jul 19 20:46:02 rachel kernel: hub: port 3 is removable
Jul 19 20:46:02 rachel kernel: hub: port 4 is removable
Jul 19 20:46:02 rachel kernel: hub: local power source is good
Jul 19 20:46:02 rachel kernel: hub: no over current condition exists
Jul 19 20:46:02 rachel kernel: enabling power on all ports
Jul 19 20:46:02 rachel kernel: uhci_connect_change: called for 1
.......
Jul 19 20:46:02 rachel kernel: hub: port 3 connection change
.......
OHCI and OHCI-HCD should give similar results. Don't worry about
failing transfers, this is a minor bug that shouldn't affect anything.
If there isn't anything that could be USB related (lines that mention
hubs, usb, ohci or uhci), likely causes are use of the wrong driver
(UHCI when you needed OHCI or OHCI when you needed UHCI), not
physically installing the hardware, a BIOS configuration that disables
USB or stuffing up the configuration or installation of the kernel.
_________________________________________________________________
Mouse Configuration
Firstly check that your mouse is being correctly sensed by the kernel.
If you type more /proc/interrupts , you should see a line that refers
to USB - typically ohci-usb or usb . If you click the mouse a few
times, and then have a look at /proc/interrupts the count associated
should increase (by two per click, one for down and one for up). This
count is a bit difficult to do with UHCI, since you have to subtract
the number of seconds that have elapsed between the checks of
/proc/interupts, and if you are using a USB keyboard, you need to
adjust for the key-presses as well.
You need to set up a /dev entry for the mouse. Use the following
command:
mknod /dev/usbmouse0 c 180 16
If you want to use the mouse under X, you need to:
* edit the XF86Config file (usually /usr/X11R6/lib/X11/XF86Config).
Add the following (anywhere sensible, ideally in the Input devices
area).
Section "Xinput"
SubSection "Mouse"
DeviceName "USB Mouse"
Protocol "IMPS/2"
Port "/dev/usbmouse0"
AlwaysCore
EndSubSection
EndSection
* Restart the X server. If you don't have any mouse support at this
point, remember that Ctrl-Alt-F1 will get you a virtual terminal
that you can use to kill the xserver and start debugging from the
error messages
If you want to use the mouse under gpm, run gpm -m /dev/usbmouse0 -t
imps2 (as superuser remember). You can make this the default if you
edit the initialisation files. These are typically named something
like rc.d and are in /etc/rc.d/ on RedHat distributions.
_________________________________________________________________
USB HP Scanner Support
The HP Scanner is capable of supporting some, but not all, HP
scanners. In particular, the HP4200 is not supported. The HP4100C,
HP5100C and HP6300C are supported.
You need to create an appropriate device file entry, using commands
(as root) like the following:
mknod /dev/usbscanner c 180 48
chmod a+rw /dev/usbscanner
To use the scanner device, you will need a suitable tool. SANE is
strongly recommended. If you don't already have it installed or your
installation is old, you will need to retrieve the package from the
closest of the sites referenced at
[5]http://www.mostang.com/sane/source.html.
For instructions on building and installing SANE, refer to the various
README files within the SANE distribution.
If you selected the default install location, SANE's configuration
files are located in /usr/local/etc/sane.d/. You need to change one of
the files - /usr/local/etc/sane.d/hp.conf to contain just the
following two lines:
/dev/usbscanner
option connect-device
You should now be able to use SANE (xscanimage or scanimage) to scan
images. You may need to specify what device you are using as a command
line option (-d) to scanimage. Much more information is available in
the various SANE man pages, including how to get [6]GIMP and
xscanimage working together.
_________________________________________________________________
Keyboard Configuration
You may not need any operating system support at all to use a USB
keyboard if you have a PC architecture. There are several BIOSs
available where the BIOS can provide USB support from a keyboard
plugged into the root hub on the motherboard. This may or may not work
through other hubs and does not normally work with add-in boards, so
you might want to add in support anyway.
Check that your keyboard is being correctly sensed by the kernel. If
you type more /proc/interrupts , you should see a line that refers to
USB - typically ohci-usb or usb . If you type on the keyboard and then
have a look at /proc/interrupts the count should increase, although
you may need to subtract the number of seconds that have elapsed if
you are using UHCI.
At this point, you should be able to use your USB keyboard just as for
a normal keyboard. Be aware that LILO is not USB aware, and that
unless your BIOS supports a USB keyboard, you may not be able to
select a non-default boot image using the USB keyboard. I personally
use only a USB keyboard (and USB mouse) and have no problems.
_________________________________________________________________
USB Audio Support
To be added.
_________________________________________________________________
Abstract Control Model Support
You need to set up /dev entries for the various ACM device. Use the
following commands:
mknod /dev/ttyACM0 c 166 0
mknod /dev/ttyACM1 c 166 1
mknod /dev/ttyACM2 c 166 2
mknod /dev/ttyACM3 c 166 3
You should now be able to use a terminal emulator program to attach to
this device and connect to your modem or other terminal device.
Apparently this driver is mostly working, but I have not personally
tested it.
_________________________________________________________________
Printer Support
You need to set up a /dev entry for the printer. Use the following
command:
mknod /dev/usblp0 c 180 0
You should now be able to use this device in a normal /etc/printcap
entry. I find this driver to be pretty good, although perhaps a bit
slow. I recommend use of automated tools to generate such files, such
as RedHat's control panel print-tool.
If this does not appear to work, check that you have actually loaded
the module, and double-check the /etc/printcap entry - especially that
the device file matches the one you just created.
_________________________________________________________________
USB Belkin and Peracom serial port support
This serial driver currently only works with the Belkin and Peracom
USB Serial devices. It should also work for the Etek converter, but
the vendor and product ID are not yet known. If you have an Etek
converter, please send the appropriate parts of /proc/bus/usb/device
(see below) to the author (<[7]greg@kroah.com>).
The serial port driver uses a major number of 240, which is in the
local/experimental range. Up to four serial ports are supported. To
create the appropriate device entries, use the following commands:
mknod /dev/ttyUSB0 c 240 0
mknod /dev/ttyUSB1 c 240 1
mknod /dev/ttyUSB2 c 240 2
mknod /dev/ttyUSB3 c 240 3
You should now be able to plug in a serial device into the adapter,
and use the /dev/ttyUSB0 just as if it were a normal serial port.
_________________________________________________________________
CPiA imager support
This driver supports a certain chipset made by Vision, and used in a
range of USB cameras (notably the Creative WebCamII). You can see the
range of products at
[8]http://www.vvl.co.uk/products/oems/videoconferencing.htm. To make
the CPiA imager work, you also need to select Video For Linux support
(under Character Devices if using menuconfig).
You need to set up a /dev entry for the CPiA camera. Use the following
command:
mknod /dev/video0 c 81 0
ln -s /dev/video0 /dev/video
To use the device, you need some video tools. There are a fairly wide
range of tools available. [9]http://millenium.diads.com/bdirks has a
package that is a generally named something like apps19990527.tgz,
depending on the date of release. It has both X and text-mode tools.
Using the text mode tools will allow you to do things like
./vctrl 320x240x24
./vcat | rawtoppm -bgr 320 240 | xv -
These tools default to using /dev/video if not otherwise specified,
hence the symbolic link made previously.
I have had serious problems making this work, although more capable
user have reported good success. If you want to work on it, you should
check the Vision CPiA website at
[10]http://home.eunet.no/~jtotland/vision
_________________________________________________________________
USB Kodak DC-2xx Camera Support
To be added.
_________________________________________________________________
Mass Storage Devices
The mass storage device driver can potentially be used with a wide a
wide range of USB devices, not all of which would normally be
considered to be mass storage. This is because the driver is really an
interface between the USB stack and the SCSI layer. Despite this, the
instructions in this section are oriented around devices like USB
floppy drives, Zip drives, LS120 drives and USB CDROMs.
Since the mass storage driver presents the USB device as a SCSI
device, you need to turn on SCSI support, which is under SCSI support
in the configuration script.
After you have compiled the kernel and rebooted (or added the relevant
modules, which includes usb-scsi in this case), you should check
/proc/scsi/scsi. Information about your device should be listed. If it
isn't, you will need to type the following, as root:
echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi
You need to make an entry in /etc/fstab. A suitable entry for a floppy
disk would be:
/dev/sda /mnt/usbfd auto noauto,user 0 0
A suitable entry for a Zip disk would be:
/dev/sda /mnt/usbzip vfat noauto,user 0 0
A suitable entry for a CDROM disk would be:
/dev/sda /mnt/usbcdrom iso9660 ro,noauto,user 0 0
A suitable entry for a hard disk would be:
/dev/sda /mnt/usbhd ext2 defaults 1 2
Note that the above entries assume you have no other SCSI devices. If
you do have other devices, then the USB mass-storage device may not be
/dev/sda, but could instead be /dev/sdb, /dev/sdc or some other
device. You would then need to substitute the right device entry for
/dev/sda in the entries above.
Having created the entr[y/ies] in /etc/fstab, you need to create
matching mount point[s] in the actual filesystem. So if you made an
entry as shown above for the USB floppy disk, then the mount point
would be made (as root) by:
mkdir /mnt/usbfd
You should now be able to mount your floppy disk with a command like:
mount /mnt/usbfd
or like:
mount /dev/sda
_________________________________________________________________
EZUSB driver
To be added.
_________________________________________________________________
USS720 driver
The USS720 is a USB to Parallel port chip made by Lucent that normally
acts like a USB Printer Class device. Indeed you can use a USS720
based bridge and a parallel port printer with the USB Printer driver,
see above. However there is also a mode (known as register mode) which
makes the USS720 look like normal parallel port hardware. This driver
makes use of that mode.
If you have the opportunity, look at /proc/sys/dev/parport before you
load the module or reboot with a kernel with USS720 enabled. You
should note the number of parallel ports you have - typically one,
under /proc/sys/dev/parport/parport0. After you put USS720 support
into your kernel, you should have another port (perhaps
/proc/sys/dev/parport1). If you look at the appropriate hardware
entry, you should see something like the following:
[bradh@rachel bradh]$ more /proc/sys/dev/parport/parport1/hardware
base: 0x0
irq: none
dma: none
modes: PCSPP,TRISTATE,COMPAT,EPP,ECP
Every distribution should have /dev entries for parallel ports -
typically /dev/lpX or /dev/parX, where the X is some number. If in
doubt, parallel ports use character major number 6.
You should now be able to use the USS720 for anything that you would
normally need a parallel port for. As for a real USB printer, I
suggest use of automated tools to generate a /etc/printcap entry if
you are connecting up a printer.
If you didn't get to select USS720 support at the configuration stage,
you need to turn on Parallel port support support (under General setup
if using menuconfig).
_________________________________________________________________
USB /proc driver
To get /proc support for the USB system, you currently need to select
Preliminary /proc/bus/usb support. Then recompile and reinstall as
detailed above.
There are multiple interfaces to the /proc support for USB.
/proc/bus/usb/drivers lists all loaded and registered drivers.
/proc/bus/usb/devices shows the currently connected devices and
certain of their attributes. There is also a tiered directory
structure of the USB busses and attached devices. Each host controller
(bus head end) is represented by a subdirectory of /proc/bus/usb,
beginning with /proc/bus/usb/000 and incrementing for each attached
host controller. Inside this subdirectory is a file for each device,
named according to that devices three digit device number. So the
third USB device on the first bus is /proc/bus/usb/000/002.
/proc/bus/usb/drivers just lists the currently registered drivers
(even if the driver is not being used by any device). This is most
useful when testing module installation, and checking for USB support
in an unknown kernel. Here is an example of its use:
[bradh@rachel bradh]$ more /proc/bus/usb/drivers
hub
printer
keyboard
mouse
/proc/bus/usb/devices lists information about the devices currently
attached to the USB bus. This is very useful when trying to figure out
if the device is correctly enumerated. Here is an example of its use,
showing the root hub, a hub, a keyboard, a mouse and a printer
adapter:
T: Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= -1 Spd=12 If#= 0 MxCh= 2 Driver=(root
hub)
T: Lev=01 Prnt=00 Port=00 Cnt=01 Dev#= 1 Spd=12 If#= 0 MxCh= 4 Driver=hub
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0451 ProdID=1446 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Lev=02 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 If#= 0 MxCh= 0 Driver=print
er
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0729 ProdID=1284 Rev= 1.04
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=07(print) Sub=01 Prot=01
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
I: If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
I: If#= 0 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 4 Ivl= 1ms
T: Lev=02 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=1.5 If#= 0 MxCh= 0 Driver=keybo
ard
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=045e ProdID=000b Rev= 0.82
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms
T: Lev=02 Prnt=01 Port=02 Cnt=03 Dev#= 4 Spd=1.5 If#= 0 MxCh= 0 Driver=mouse
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c001 Rev= 1.10
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 50mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms
The information in the /proc/bus/usb/devices output is arranged in
groups:
* The line that starts with T: is the topology. Lev indicates the
level of the device, starting at level 00 for the root hub, level
01 for any device attached to the root hub, level 02 for devices
attached to hubs at level 01, and so on. Prnt is the parent device
for this device (always 00 for the root hub and any device
attached to the root hub). Port is the port on the parent device,
starting at 00 for the first port on each device. Prnt/Port is
unique per bus. Cnt indicates what number device this is, at this
level, based on the enumeration order within that level of the
topology, starting at 01 for the first device. Dev# indicates what
number device this is, irrespective of level, based on the bus
enumeration order. Spd indicates what speed this device is running
at, in Mbps (either 1.5 or 12 with the current version of USB).
If# indicates what number interface is currently selected. MxCh
indicates how many devices can be connected to this device, and is
00 for anything except a hub. Driver indicates which device driver
is being used for this device - an entry of (none) indicates that
no driver is being used.
* The line that starts with D: is information from the device
descriptor. Ver indicates which USB specification version the
device claims to meet. Cls indicates which device class the device
is claiming to meet, in both hexadecimal and as a string. A Cls
entry of 00(>ifc) indicates that the device class specification
compliance is interface dependent, and the interface descriptor
should be read for device class information. Sub indicates which
sub-class (within the Cls entry), the device meets. MxPS indicates
how big the packets from Endpoint 0 are. #Cfgs indicates how many
configurations this device has.
* Much like D:, the line that starts with P: is information from the
device descriptor, and is seperated mainly because it wouldn't all
fit on one line. Vendor indicates the Vendor Identification code
for the device, and ProdID indicates the Product Identification
code for the device. Rev indicates the product revision number.
* Refer to the USB specification clause 9.7.1 for further
information on device descriptors.
* The line that starts with C: is information from the configuration
descriptor - the number of C:lines per device is given by #Cfgs,
and the entry followed by an asterisk is the current
configuration. #If indicates how many interfaces the device has.
Cfg# indicates which configuration is being described. Atr is a
hexadecimal indication of the device attributes (0x80 for
bus-powered, 0x40 for self-powered, 0x20 for remote wake-up
capable). MPwr is the maximum power draw for this device
configuration, in milliamps. Refer to USB specification clause
9.7.2 for further information on configuration descriptors.
* The line that starts with I: is information from the interface
descriptor - the number of I: lines per C: line is given by the
#Ifs entry. If# indicates which interface is being described
within a given device configuration. Alt indicates which alternate
setting of this interface is being described. #EPs indicates how
many endpoints there are within the alternate setting for this
endpoint. Cls indicates which class the alternate setting of the
interface corresponds to, in both hexadecimal and as a character
string. Sub indicates which sub-class the alternate setting of the
interface belongs to. Prot indicates which interface protocol
(within a class and sub-class tuple) the alternate setting of the
interface conforms to. See USB specification clause 9.7.3 for
further information.
* The line that starts with E: is information from the interface
descriptor - the number of E: lines per I: line is given by the
#EPs entry. Endpoint 0 is not displayed. Ad indicates the endpoint
address, with a letter to indicate whether the endpoint is an In
or Out endpoint. Atr indicate the attribute (transfer type)
associated with the endpoint, followed by a string translating the
transfer type. MxPS indicates the maximum packet size this
endpoint is capable of sending or receiving, as appropriate. For
isochronous transfers, MxPS indicates how much bandwidth needs to
be reserved. Ivl indicates the interval, in milliseconds, between
polling of interrupt endpoints. Ivl is ignored for bulk and
control transfers, and is set to 1 for isochronous transfers. See
USB specification clause 9.7.4 for further information on endpoint
descriptors.
Refer to linux/Documentation/proc_usb_format.txt for more information
on using the /proc/bus/usb information.
_________________________________________________________________
Frequently Asked Questions
There certain questions that keep reappearing. This section tries to
answer those questions.
_________________________________________________________________
How do I report a bug?
In addition to the information required in
/usr/src/linux/REPORTING-BUGS, it also helps enormously if you provide
the output of /proc/bus/usb/devices. If you are having problems with
your host controller being recognised, it helps to have the output of
lspci -v. If it is supposed to be UHCI, it helps to know whether
interrupts are being generated every second.
_________________________________________________________________
How do I write a driver?
You study the kernel source. You find a driver that is similar to what
you need to do, and you adapt it till it works. In this context,
similar is in terms of what transfers you need to do, not in what the
device looks like.
_________________________________________________________________
What is a good book on USB
I have only read one, and thought it was very poor. I suggest that you
get the specifications from [11]http://www.usb.org, which are at no
cost, are quite readable, and are up to date.
_________________________________________________________________
I have a vendor specific device, here is the descriptors
The descriptors are essential, but not sufficient, to write a driver.
You need the low level design detail from the vendor. In addition,
don't be surprised if the descriptor is not specification compliant -
all bets are off with vendor devices. Remember that descriptors are
just data bytes from the device, and reprogramming the device can make
any text appear, irrespective of what the device is really capable of.
_________________________________________________________________
What major and minor numbers should I use for my driver?
The primary major is 180, and the minors are assigned in groups of 16.
Don't overlap with someone else, and do consider using something than
180 if you are using USB as a transport for something else (e.g. USB
video should and does use a major of 81.
USB ACM (serial communications) uses 166 and 167.
_________________________________________________________________
How do I make USB work on my Sony Vaio laptop?
You need to turn off the BIOS option for Plug-n-Pray operating system
support. Then it should work fine, although you may have problems with
a modem.
_________________________________________________________________
Where can I get the latest version of this HOWTO?
From [12]http://www.dynamine.net/linux-usb/HOWTO or from From
[13]http://linuxkb.cheek.com/pages/usb-howto.
You can get the SGML source by emailing the author. Translations into
French, Japanese and Korean are in progress.
_________________________________________________________________
Corrections
Please send comments on this document to the author, preferably by
E-Mail (<[14]brad.hards@defence.gov.au>), including the version
number: ($Revision: 0.9.0 $).
References
1. mailto:linux-usb@suse.com
2. mailto:majordomo@suse.com
3. mailto:majordomo@suse.com
4. http://www.suse.cz/development/usb-backport/
5. http://www.mostang.com/sane/source.html
6. http://www.gimp.org/
7. mailto:greg@kroah.com
8. http://www.vvl.co.uk/products/oems/videoconferencing.htm
9. http://millenium.diads.com/bdirks
10. http://home.eunet.no/~jtotland/vision
11. http://www.usb.org/
12. http://www.dynamine.net/usb/HOWTO
13. http://linuxkb.cheek.com/pages/usb-howto
14. mailto:brad.hards@defence.gov.au
--
To unsubscribe, e-mail: linux-usb-unsubscribe@suse.com
For additional commands, e-mail: linux-usb-help@suse.com