install.sgml

usb develop guide

        a separate "Open Digita Services" project which can be used to
        do that.  See that project's web site, at
        <ulink url="http://ods.sourceforge.net/">ods.sourceforge.net</ulink>.
        </para>

        <para> (There are also various Perl and Python scripts available
        to provide some of this functionality, if you prefer to develop
        in those languages rather than in C.) </para>

        </sect2>

    <sect2> <title>Other Approaches (Developers only)</title>

        <para>The solutions described above are, at this writing, the
        most widely used ones.  You may be interested to know about
        some other solutions that might work. </para>

        <para> You can configure the <emphasis>usbserial</emphasis>
        module with "generic serial" driver support.  This lets you
        provide kernel module parameters that let the serial driver
        handle specific bulk-only devices (using USB product and
        vendor IDs).  The Kodak or ODS cameras mentioned above are
        bulk-only, so this might permit <filename>/dev/usb/ttyN</filename>
        style paths to work instead of <filename>/dev/usb/dc2xxN</filename>
        style ones.</para>

        <para> Systems which enable the "prototype usbdevfs" support
        can configure it to allow appropriately intelligent user
        mode programs to access USB devices.  This requires libraries
        that know how to interact with <filename>/proc/bus/usb/NNN/MMM</filename>
        files for each USB device, ways to address security issues that
        arise (programs need read/write access), and ways to have
        user and kernel mode software interact safely.  Such work
        is under way.  See for example the Java USB project  at
        <ulink url="http://jusb.sourceforge.net/">jusb.sourceforge.net</ulink>
        and the C "libusb" at <ulink
        url="http://libusb.sourceforge.net/">libusb.sourceforge.net</ulink>
        </para>

        </sect2>

    </sect1>

<Sect1><Title>Mass Storage Devices</>
<Para>
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.
</>

<Para>
Since the mass storage driver presents the USB device as a SCSI
device, you need to turn on <UserInput>SCSI support</UserInput>, which
is under <UserInput>SCSI support</UserInput> in the configuration
script. You should also turn on subordinate options as appropriate to
your mass storage device - usually one or more of <UserInput>SCSI disk
support</userinput>, <Userinput>SCSI tape support</userinput>,
<userinput>SCSI CD-ROM support</userinput> and <userinput>SCSI generic
support</userinput>.
</>

<Para>
After you have compiled the kernel and rebooted (or added the relevant
modules, which is <FileName>usb-storage.o</FileName>),
you should check <FileName>/proc/scsi/scsi</FileName>. Information
about your device should be listed. 
</>

<para>
You can now mount your device. The exact syntax depends on the device
type. The best way is to make suitable entries in
<FileName>/etc/fstab</FileName>. A suitable entry for a floppy disk
would be: 
<screen>
/dev/sda    /mnt/usbfd       auto            noauto,user 0   0
</screen>
</>

<Para>
A suitable entry for a Zip disk would be:
<screen>
/dev/sda4    /mnt/usbzip      vfat            noauto,user 0   0
</screen>
</>

<Para>
A suitable entry for a CDROM disk would be:
<screen>
/dev/scd0    /mnt/usbcdrom    iso9660         ro,noauto,user 0   0
</screen>
</>

<Para>
A suitable entry for a hard disk with a single partition would be:
<screen>
/dev/sda1    /mnt/usbhd       ext2            defaults   1   2
</screen>
</>

<Para>
Note that the above entries assume you have no other SCSI devices. If
you do have other devices, then the USB disk may not be
<FileName>/dev/sda</FileName>, but could instead be
<FileName>/dev/sdb</FileName>, <FileName>/dev/sdc</FileName> or some
other device. You would then need to substitute the right device entry
for <FileName>/dev/sda</FileName> or <filename>/dev/scd0</filename>
in the entries above.
</>

<Para>
Having created the entr[y/ies] in <FileName>/etc/fstab</FileName>, 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:
<screen>
mkdir /mnt/usbfd
</screen>
</>

<Para>
You should now be able to mount your floppy disk with a command like:
<screen>
mount /mnt/usbfd
</screen>
or like:
<screen>
mount /dev/sda
</screen>
</>

</Sect1>

<Sect1><Title>USS720 driver</>
<Para>
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.
</>

<Para>
If you have the opportunity, look at
<UserInput>/proc/sys/dev/parport</UserInput> 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
<UserInput>/proc/sys/dev/parport/parport0</UserInput>. After you put
USS720 support into your kernel, you should have another port (perhaps
<UserInput>/proc/sys/dev/parport1</UserInput>). If you look at the
appropriate <UserInput>hardware</UserInput> entry, you should see
something like the following:
<screen>
[bradh@rachel bradh]$ more /proc/sys/dev/parport/parport1/hardware
base:   0x0
irq:    none
dma:    none
modes:  PCSPP,TRISTATE,COMPAT,EPP,ECP
</screen>
</>

<Para>
Every distribution should have device node entries
for parallel ports - typically <UserInput>/dev/lpX</UserInput> or
<UserInput>/dev/parX</UserInput>, where the <UserInput>X</UserInput>
is some number. If you need to create them, parallel ports device nodes
use character major number 6.
</>

<Para>
You should now be able to use the USS720 for anything that you would
normally need a parallel port for, except that certain timing sensitive
applications may not work, since the emulation is rather slow.
As for a real USB printer, I suggest use of automated tools to generate a
<UserInput>/etc/printcap</UserInput> entry if you are connecting up a
printer.
</>

<Para>
If you didn't get to select USS720 support at the configuration stage,
you need to turn on <UserInput>Parallel port support</UserInput>
support (under <UserInput>General setup</UserInput> if using
<UserInput>menuconfig</UserInput>).
</>

</Sect1>

<Sect1><Title>DABUSB driver</>
<para>
This device requires hardware that has not yet been released,
and is currently provided mainly to show how to write a driver.
For more information, see
<ulink url="http://dab.in.tum.de">http://dab.in.tum.de</ulink>.
</>
</Sect1>

<Sect1><title>PLUSB Prolific USB-Network driver</>
<para>
Prolific manufacture a range of USB chips, including the
<ulink url="http://www.prolific.com.tw/pl2301.htm">PL2301</ulink> and
<ulink url="http://www.prolific.com.tw/pl2302.htm">PL2302</ulink> devices
that allow two USB host controllers to be linked, providing a simple
point to point link at up to 5Mbps. This driver supports both PL2301 andPL2302
chips.
</>

<para>
Aserton, Bencent, Butterfly, Camtel, Longshine, Prolific, Share Plus,
SIIG, StarMount, Swann, Univex, USBdevices and VVMer cables are all
known to use the PL2301 or PL2302 chips. 
Entrega, Xircom and Belkin adapters do not use Prolific chips and are not
supported by this driver.
</para>

<para>
In addition to selecting this option to either be compiled into the kernel
or to be build as a module, you need to configure the appropriate networking
interfaces. If you have two machines (say <SystemItem>zhora</systemitem> and
<systemitem>rachel</systemitem>, then on <SystemItem>zhora</systemitem> you
would enter <UserInput>ifconfig plusb0 192.168.0.1 pointopoint 192.168.0.2
</UserInput>. On  <systemitem>rachel</systemitem> you would enter
<UserInput>ifconfig plusb0 192.168.0.2 pointopoint 192.168.0.1
</UserInput>. To test that it is working, on <SystemItem>zhora</systemitem>,
enter <UserInput>ping 192.168.0.2</userinput>. If you get packets back, it
is working correctly.
</para>

<para>
For further information on networking, I suggest that you refer to the
many excellent Linux networking documents, including the
<ulink url="http://www.linuxdoc.org/LDP/nag/nag.html">Linux Network Administrators'
Guide</ulink> and the  <ulink url="http://www.linuxdoc.org/HOWTO/Net-HOWTO/index.html">
Linux Network HOWTO</ulink>.
</para>
</Sect1>

<Sect1><title>NetChip 1080-based USB Host-to-Host Link</>
<para>
Netchip manufactures a range of USB devices, including the 1080, which
provides direct connection between two USB hosts.
</>

<para>
In addition to selecting this option to either be compiled into the kernel
or to be build as a module, you need to configure the appropriate networking
interfaces. If you have two machines (say <SystemItem>zhora</systemitem> and
<systemitem>rachel</systemitem>, then on <SystemItem>zhora</systemitem> you
would enter <UserInput>ifconfig usb0 192.168.0.1 pointopoint 192.168.0.2
</UserInput>. On  <systemitem>rachel</systemitem> you would enter
<UserInput>ifconfig usb0 192.168.0.2 pointopoint 192.168.0.1
</UserInput>. To test that it is working, on <SystemItem>zhora</systemitem>,
enter <UserInput>ping 192.168.0.2</userinput>. If you get packets back, it
is working correctly.
</para>

<para>
For further information on networking, I suggest that you refer to the
many excellent Linux networking documents, including the
<ulink url="http://www.linuxdoc.org/LDP/nag/nag.html">Linux Network Administrators'
Guide</ulink> and the  <ulink url="http://www.linuxdoc.org/HOWTO/Net-HOWTO/index.html">
Linux Network HOWTO</ulink>.
</para>
</Sect1>

<Sect1><title>USB ADMtek Pegasus-based device support</>
<para>
This driver suppport a range of ethernet adapters based on a chipset
produce by ADMtek. Just about all adapters that provide 10/100BaseT are
based on this chipset.
</>

<para>
In addition to selecting this option to either be compiled into the kernel
or to be build as a module, you need to configure the appropriate networking
interfaces. The device will appear as another ethernet device, and can be checked
using entries like <UserInput>cat /proc/net/dev</UserInput> or tools like
<command>ifconfig</command>.
</para>

<para>
For further information on networking, I suggest that you refer to the
many excellent Linux networking documents, including the
<ulink url="http://www.linuxdoc.org/LDP/nag/nag.html">Linux Network Administrators'
Guide</ulink> and the  <ulink url="http://www.linuxdoc.org/HOWTO/Net-HOWTO/index.html">
Linux Network HOWTO</ulink>.
</para>
</Sect1>

<Sect1><Title>USB Diamond Rio500 support </Title>
<para>
To be done. See   <ulink url="http://rio500.sourceforge.net">
http://rio500.sourceforge.net</ulink>
</para>
</Sect1>

<Sect1><Title>D-Link USB FM radio support</Title>
<para>
The D-Link USB FM radio driver uses the Video4Linux interface, similar
to the webcams discussed above.
</para>

<para>
If the appropriate device node entries do not exist, you should create them:
<screen>
mknod /dev/video0 c 81 0
mknod /dev/video1 c 81 1
mknod /dev/video2 c 81 2
mknod /dev/video3 c 81 3
ln -s /dev/video0 /dev/video
</screen>
</para>

<para>
After plugging the radio in, all you should you need to do is to start up
an appropriate application - I normally use kradio and KTuner from KDE, although
any Video4Linux radio application should work successfully.
</para>
</Sect1>


</Chapter>