| 1 |
.TH sane\-find\-scanner 1 "13 Jul 2008" "" "SANE Scanner Access Now Easy" |
| 2 |
.IX sane\-find\-scanner |
| 3 |
.SH NAME |
| 4 |
sane\-find\-scanner \- find SCSI and USB scanners and their device files |
| 5 |
.SH SYNOPSIS |
| 6 |
.B sane\-find\-scanner |
| 7 |
.RB [ \-? | \-h | \-\-help ] |
| 8 |
.RB [ \-v ] |
| 9 |
.RB [ \-q ] |
| 10 |
.RB [ \-p ] |
| 11 |
.RB [ \-f ] |
| 12 |
.RB [ \-F |
| 13 |
.IR filename ] |
| 14 |
.RI [ devname ] |
| 15 |
|
| 16 |
.SH DESCRIPTION |
| 17 |
.B sane\-find\-scanner |
| 18 |
is a command-line tool to find SCSI and USB scanners and determine their UNIX |
| 19 |
device files. Its primary aim is to make sure that scanners can be detected by |
| 20 |
SANE backends. |
| 21 |
.PP |
| 22 |
For |
| 23 |
.B SCSI |
| 24 |
scanners, it checks the default generic SCSI device files (e.g., |
| 25 |
.IR /dev/sg0 ) |
| 26 |
and |
| 27 |
.IR /dev/scanner . |
| 28 |
The test is done by sending a SCSI inquiry command and looking for a device |
| 29 |
type of "scanner" or "processor" (some old HP scanners seem to send |
| 30 |
"processor"). So |
| 31 |
.B sane\-find\-scanner |
| 32 |
will find any SCSI scanner connected to those default device files even if it |
| 33 |
isn't supported by any SANE backend. |
| 34 |
.PP |
| 35 |
For |
| 36 |
.B USB |
| 37 |
scanners, first the USB kernel scanner device files (e.g. |
| 38 |
.IR /dev/usb/scanner0 , |
| 39 |
.IR /dev/usb/scanner , |
| 40 |
and |
| 41 |
.IR /dev/usbscanner ) |
| 42 |
are tested. The files are opened and the vendor and device ids are determined, |
| 43 |
if the operating system supports this feature. Currently USB scanners are only |
| 44 |
found this way if they are supported by the Linux scanner module or the |
| 45 |
FreeBSD or OpenBSD uscanner driver. After that test, |
| 46 |
.B sane\-find\-scanner |
| 47 |
tries to scan for USB devices found by the USB library libusb (if |
| 48 |
available). There is no special USB class for scanners, so the heuristics used |
| 49 |
to distinguish scanners from other USB devices is not |
| 50 |
perfect. |
| 51 |
.B sane\-find\-scanner |
| 52 |
also tries to find out the type of USB chip used in the scanner. If detected, |
| 53 |
it will be printed after the vendor and product ids. |
| 54 |
.B sane\-find\-scanner |
| 55 |
will even find USB scanners, that are not supported by any SANE backend. |
| 56 |
.PP |
| 57 |
.B sane\-find\-scanner |
| 58 |
won't find most |
| 59 |
parallel port scanners, or scanners connected to proprietary ports. Some |
| 60 |
.B parallel port |
| 61 |
scanners may be detected by |
| 62 |
.I "sane\-find\-scanner -p" . |
| 63 |
At the time of writing this will only detect Mustek parallel port scanners. |
| 64 |
|
| 65 |
.SH OPTIONS |
| 66 |
.TP 8 |
| 67 |
.B \-?, \-h, \-\-help |
| 68 |
Prints a short usage message. |
| 69 |
.TP 8 |
| 70 |
.B \-v |
| 71 |
Verbose output. If used once, |
| 72 |
.B sane\-find\-scanner |
| 73 |
shows every device name and the test result. If used twice, SCSI inquiry |
| 74 |
information and the USB device descriptors are also printed. |
| 75 |
.TP 8 |
| 76 |
.B \-q |
| 77 |
Be quiet. Print only the devices, no comments. |
| 78 |
.TP 8 |
| 79 |
.B \-p |
| 80 |
Probe parallel port scanners. |
| 81 |
.TP 8 |
| 82 |
.B \-f |
| 83 |
Force opening all explicitly given devices as SCSI and USB devices. That's |
| 84 |
useful if |
| 85 |
.B sane\-find\-scanner |
| 86 |
is wrong in determining the device type. |
| 87 |
.TP 8 |
| 88 |
.B \-F filename |
| 89 |
filename is a file that contains USB descriptors in the format of |
| 90 |
/proc/bus/usb/devices as used by Linux. |
| 91 |
.B sane\-find\-scanner |
| 92 |
tries to identify the chipset(s) of all USB scanners found in such a file. This |
| 93 |
option is useful for developers when the output of |
| 94 |
.I "cat /proc/bus/usb/devices" |
| 95 |
is available but the scanner itself isn't. |
| 96 |
.TP 8 |
| 97 |
.B devname |
| 98 |
Test device file "devname". No other devices are checked if devname is given. |
| 99 |
.SH EXAMPLE |
| 100 |
.I sane\-find\-scanner \-v |
| 101 |
.br |
| 102 |
Check all SCSI and USB devices for available scanners and print a line for |
| 103 |
every device file. |
| 104 |
.PP |
| 105 |
.I sane\-find\-scanner /dev/scanner |
| 106 |
.br |
| 107 |
Look for a (SCSI) scanner only at /dev/scanner and print the result. |
| 108 |
.PP |
| 109 |
.I sane\-find\-scanner \-p |
| 110 |
.br |
| 111 |
Probe for parallel port scanners. |
| 112 |
.SH "SEE ALSO" |
| 113 |
.BR sane (7), |
| 114 |
.BR sane\-scsi (5), |
| 115 |
.BR sane\-usb (5), |
| 116 |
.BR scanimage (1), |
| 117 |
.BR xscanimage (1), |
| 118 |
.BR xsane (1), |
| 119 |
.BR sane\-"backendname" (5) |
| 120 |
|
| 121 |
.SH AUTHOR |
| 122 |
Oliver Rauch, Henning Meier-Geinitz and others |
| 123 |
.SH SUPPORTED PLATFORMS |
| 124 |
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, |
| 125 |
libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor and |
| 126 |
device ids only works with Linux or libusb. |
| 127 |
.PP |
| 128 |
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, |
| 129 |
NetBSD, OpenBSD, and HP-UX. |
| 130 |
|
| 131 |
.SH BUGS |
| 132 |
No support for most parallel port scanners yet. |
| 133 |
.br |
| 134 |
Detection of USB chipsets is limited to a few chipsets. |