install.sgml

usb develop guide

print-tool.I find this driver to be pretty good, although perhaps a
bit slow.
</>

<para>
If this does not appear to work, check that you have actually 
loaded the module, and double-check the <FileName>/etc/printcap</FileName>
entry - especially that the device file matches the one you just
created. Also note that some printers require special control
characters to be sent to the printer to get the USB interface to be
made operational. This is printer specific.
</>

</Sect1>

<Sect1><Title>USB Serial Converter support</>
<Para>
This serial driver supports a wide range of USB to serial adapters. It
also allows communication with the Handspring Visor. You need to turn on
<UserInput>USB Serial Converter support</UserInput>, and then select
whichever of the various particular drivers you need. The
<UserInput>Generic Serial Driver</UserInput> can be used with a wide
range of converters, by specifying the vendor and product ID codes when
you load the USB serial converter module:
<UserInput>insmod usb-serial.o vendor=0xVVVV product-0xPPPP</UserInput>,
where you need to change the <UserInput>VVVV</UserInput> and
<UserInput>PPPP</UserInput> to match your device.
</>

<para>
The serial port driver uses a major number of 188. Up to sixteen serial
ports are supported. To create the appropriate device entries, use the
following commands:
<screen>
mknod /dev/usb/ttyUSB0 c 188 0
mknod /dev/usb/ttyUSB1 c 188 1
mknod /dev/usb/ttyUSB2 c 188 2
mknod /dev/usb/ttyUSB3 c 188 3
mknod /dev/usb/ttyUSB4 c 188 4
mknod /dev/usb/ttyUSB5 c 188 5
mknod /dev/usb/ttyUSB6 c 188 6
mknod /dev/usb/ttyUSB7 c 188 7
mknod /dev/usb/ttyUSB8 c 188 8
mknod /dev/usb/ttyUSB9 c 188 9
mknod /dev/usb/ttyUSB10 c 188 10
mknod /dev/usb/ttyUSB11 c 188 11
mknod /dev/usb/ttyUSB12 c 188 12
mknod /dev/usb/ttyUSB13 c 188 13
mknod /dev/usb/ttyUSB14 c 188 14
mknod /dev/usb/ttyUSB15 c 188 15
</screen>
</>

<para>
You should now be able to plug in a serial device into the adapter,
and use the <FileName>/dev/usb/ttyUSB0</Filename> just as if it were a
normal serial port.
</>

<para>
To communicate with the Handspring Visor, you need an additional application
package known as <ulink url="ftp://ryeham.ee.ryerson.ca/pub/PalmOS/pilot-link.0.9.3.tar.gz">Pilot-Xfer</>. Installation and use of this
package is covered later in this guide.
</para>

</Sect1>


<Sect1><Title>USB Cameras</>


<Sect2><Title>Generic camera configuration</>

<para>
Under Linux, USB cameras use the Video4Linux interface.
You need to set up a device node entry for the USB camera.
Use the following command, if you have no other Video4Linux
devices:
<screen>
mknod /dev/video0 c 81 0
ln -s /dev/video0 /dev/video
</screen>
</>

<para>
To use the device, you need some video tools. There are a fairly wide range
of tools available. <ulink url="http://www.thedirks.org/v4l2/">
http://www.thedirks.org/v4l2</ulink> has a package that
is a generally named something like <FileName>apps20000611.tgz</FileName>,
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
<screen>
./vctrl 320x240x24
./vcat | rawtoppm -bgr 320 240 | xv -
</screen>
These tools default to using <FileName>/dev/video</FileName> if not
otherwise specified, hence the symbolic link made previously.
</>

<para>
There are other suitable tools available. Links to some of these tools
are provided in the Linux USB web site at <ulink
url="http://www.linux-usb.org">http://www.linux-usb.org</ulink>.
</para>

</Sect2>


<Sect2><Title>USB CPiA Camera support</>
<para>
This driver supports a certain chipset made by Vision, and used
in a range of USB cameras (notably the Creative WebCamII). 
To make the CPiA camera driver work, you need to select
<UserInput>Video For Linux</UserInput> (under 
<UserInput>Multimedia devices</UserInput>), and then select
<UserInput>CPiA Video For Linux</UserInput> and
<UserInput>CPiA USB Lowlevel Support</UserInput> options within
the <UserInput>Video For Linux</UserInput>.
</>

</Sect2>

<Sect2><Title>USB OV511 Camera support</>

<para>
This driver supports a certain chipset made by OmniVision, and used
in a range of USB cameras (notably the Creative WebCam III).
To make the OV511 driver work, you  need to select
<UserInput>Video For Linux</UserInput> support (under
<UserInput>Multimedia devices</UserInput> and <UserInput>USB OV511
Camera support</UserInput> under <UserInput>USB support</UserInput>.
</>

</Sect2>

<Sect2><Title>USB IBM (Xirlink) C-it Camera support</>

<para>
This driver supports the <ulink url="http://www.c-itnow.com/">Xirlink
C-it</ulink> cameras, also sold by IBM.
To make the OV511 driver work, you also need to select
<UserInput>Video For Linux</UserInput> support (under
<UserInput>Multimedia devices</UserInput> and <UserInput>USB IBM
(Xirlink) C-it Camera support</UserInput>
</>

</Sect2>
</Sect1>


<sect1> <title>USB and Digital Still Cameras</title>

    <para> While most digital still cameras support a serial line
    at up to 115 Kbps, the fastest ways to get pictures out of your
    camera onto Linux involve USB:

    <variablelist>
        <varlistentry><term> <emphasis>
             USB Connection for Camera</emphasis></term>
            <listitem><para>Some cameras can connect directly to USB,
            normally using a custom jack on the camera, which is smaller
            than the standard type B jacks you see on the upstream side
            of hubs and other devices. </para></listitem> </varlistentry>
        <varlistentry><term><emphasis>
            USB Connection for Memory</emphasis></term>
            <listitem><para>A number of cameras don't have a direct USB
            hookup, but may come with an adapter that lets you connect
            their memory cards instead.  Those cards are accessed using
            the mass storage driver, as if they were disk drives.  (USB
            mass storage support is discussed elsewhere in this document.)
            You can buy such adapters separately; be sure that Linux supports
            the adapter model you want to use.</para></listitem> </varlistentry>
        <varlistentry><term><emphasis>
            PCMCIA Connection for Memory</emphasis></term>
            <listitem><para>Inexpensive PCMCIA adapters ($10US) let you
            treat memory cards like IDE disks.  This won't be discussed
            any further here, but you should know the option exists.  The
            transfer rate is higher than for USB, but the downside is that
            PCMCIA support is generally only available on laptops.
            </para></listitem> </varlistentry>
        </variablelist>
        </para>

    <para> Only the first of these approaches is discussed in this
    section, where the camera has a direct connection to USB.  The
    table below summarizes the most important information: </para>

    <informaltable>
        <tgroup align="left" cols="4">
            <thead>
                <row>
                    <entry>Still Camera</entry>
                    <entry>Drivers</entry>
                    <entry>Applications</entry>
                    <entry>Notes</entry>
                </row>
            </thead>
            <tbody>
                <!--
                <row>
                    <entry>Canon PowerShot S20</entry>
                    <entry>scanner</entry>
                    <entry>what are the scanner apps?</entry>
                    <entry>(pending kernel bugfixes)</entry>
                </row>
                -->
                <row>
                    <entry>Kodak DC-240/280</entry>
                    <entry>dc2xx</entry>
                    <entry> gPhoto</entry>
                    <entry>The first still cameras supported under Linux.
                        USB lets you download pictures, take new ones,
                        change camera settings, and more.  </entry>
                </row>
                <row>
                    <entry>Kodak DC-220/260/265/290,
                        HP PhotoSmart C-500</entry>
                    <entry>dc2xx</entry>
                    <entry>ODS (no GUI)</entry>
                    <entry>DigitaOS runs these cameras, letting you
                        run scripts on the camera as well as the sort
                        of functionality available on the other
                        DC-2xx series USB cameras. </entry>
                </row>
                <row>
                    <entry>Mustek MDC-800</entry>
                    <entry>mdc800</entry>
                    <entry>gPhoto</entry>
                    <entry>Only one camera at a time supported. </entry>
                </row>
                <row>
                    <entry>Sony DSC-505,
                        Toshiba PDR-M4,
                        and many USB card readers
                        </entry>
                    <entry>storage, fat filesystem</entry>
                    <entry>ls, cp, mc, &amp;c.</entry>
                    <entry>readonly for now </entry>
                </row>
            </tbody>
        </tgroup>
    </informaltable>

    <para> Your kernel may already have the <emphasis>dc2xx</emphasis>,
    <emphasis>mdc800</emphasis> and <emphasis>storage</emphasis> compiled
    as modules, or as part of the kernel.  If it doesn't, rebuild so that
    you have them available. </para>

    <sect2> <title>Filesystem Device Nodes</title>

        <para> If you use the dc2xx or mdc800 driver, you have all the security         hooks you need.  The instructions shown below assume that PAM will be
        set up to change ownership of these nodes to the logged-in user using
        the <filename>/etc/console.perms</filename> file.  If that is not done,        think carefully about the ownership and permissions you use in the
        instructions below.  (Mode 0666 works for trusted systems, such
        as single users workstations with no rlogin.) </para>

        <para> The dc2xx driver supports up to sixteen devices, but most users
        won't need to use more than one or two cameras.  If these device nodes
        aren't part of your distribution, make at least the first few of them
        as follows:
        <screen>
        # mknod -m 0660 /dev/usb/dc2xx0 c 180 80
        # mknod -m 0660 /dev/usb/dc2xx1 c 180 81
        # mknod -m 0660 /dev/usb/dc2xx2 c 180 82
        # mknod -m 0660 /dev/usb/dc2xx3 c 180 83
        ...
        # mknod -m 0660 /dev/usb/dc2xx15 c 180 95
        </screen></para>

        <para> The mdc800 driver supports one device.  If its device node
        isn't part of your distribution, make it as follows:
        <screen>
        # mknod -m 0660 /dev/usb/mdc800 c 180 32
        </screen></para>

        <para> If your connectivity uses the storage driver, see
        the section on that driver for more information. </para>

        </sect2>

    <sect2> <title>Sanity Checking </title>

        <para> After you think your kernel is set up, connect your camera to
        your computer with USB (power it up!) and check to see if a kernel
        message (perhaps in <filename>/var/log/messages</filename>)
        reports the driver saw the
        camera.  If it didn't, you can do a bit of troubleshooting if you've
        got "procfs" and the prototype "usbdevfs" code set up. </para>

        <para> The first check is whether USB is basically set up.  You
        should see the driver listed in <filename>/proc/bus/usb/drivers</filename>;
        if it's not there, use "modprobe" to load it.  There should be a
        bus directory such as <filename>/proc/bus/usb/001</filename> also; if
        there isn't, you may need to
        "modprobe" the right host controller driver (OHCI or UHCI). </para>

        <para> Then make sure that the kernel saw the camera.  With it still
        connected and powered up, check for an entry in
        <filename>/proc/bus/usb/devices</filename>
        corresponding to your camera.  (The product ID string may name it.)
        If there is no camera there, check your USB connections.  If you
        find the camera listed there, make sure it's one of the supported
        cameras.  There should be an "I: ..." line showing that driver.  For
        example, at the end of the line it would have "Driver=dc2xx",
        "Driver=mdc800", or "Driver=storage".  If you don't see that, then
        the troubleshooting gets interesting.  </para>

        </sect2>

    <sect2> <title>gPhoto </title>

        <para> gPhoto is a graphical application that knows how to talk to many         different digital cameras.  At this writing its current version (0.4.3)         knows how to use USB to talk to three cameras:
        appropriate camera model and use an "other" (non-TTY) device path
        name as shown above.  (Use dc2xx0 unless you have multiple cameras.)
        Check the "Camera Summary" to see if it's connected properly. </para>

        <para> At that point, you should be able to download thumbnails of
        all the pictures in the camera, then download the pictures you've
        chosen.  (At this writing, it's visibly faster to use OHCI than
        to use UHCI.) </para>

        <para> More information about gPhoto is available at its web site,
        <ulink url="http://www.gPhoto.org/">www.gPhoto.org</ulink>. </para>

        </sect2>

    <sect2> <title> DigitaOS Cameras and ODS </title>

        <para> At this writing, gPhoto does not know how to communicate
        with cameras using the "DigitaOS" environment.  However, there is