summaryrefslogtreecommitdiff
path: root/doc/sane-scsi.man
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff.email>2024-03-03 09:54:51 +0100
committerJörg Frings-Fürst <debian@jff.email>2024-03-03 09:54:51 +0100
commit44916ca6d75e0b5f258a098a50d659f31c6625fd (patch)
tree2e51a12ae43b3def9e55d3f2c9ca60d2032ad45c /doc/sane-scsi.man
parent84357741a6a6e6430f199b2c3f7498e0e97da9ad (diff)
New upstream version 1.3.0upstream/1.3.0
Diffstat (limited to 'doc/sane-scsi.man')
-rw-r--r--doc/sane-scsi.man14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/sane-scsi.man b/doc/sane-scsi.man
index 0cd63ca..723b286 100644
--- a/doc/sane-scsi.man
+++ b/doc/sane-scsi.man
@@ -44,7 +44,7 @@ is the SCSI vendor string,
.I MODEL
is the SCSI model string,
.I TYPE
-is type SCSI device type string,
+is the SCSI device type string,
.I BUS
is the SCSI bus number (named "host" in
.IR /proc/scsi/scsi ),
@@ -195,7 +195,7 @@ maximum buffer size can be changed at program run time, and there is no restrict
version 2.2.7 on. If the new SG driver is available some backends
(e.g.
.BR sane\-umax (5),
-.BR sane\-mustek (5) ,
+.BR sane\-mustek (5),
.BR sane\-sharp (5))
automatically request larger SCSI
buffers. If a backend does not automatically request a larger SCSI buffer, set
@@ -204,9 +204,9 @@ the environment variable
to the desired buffer size in bytes. It is not recommended to use more
than 1 MB, because for large values the probability increases that the
SG driver cannot allocate the necessary buffer(s). For ISA cards, even
-1 MB might be a too large value. For a detailed discussion of memory
-issues of the SG driver, see
-.I http://www.torque.net/sg.
+1 MB might be a too large value.
+For a detailed discussion of the Linux SG SCSI driver see:
+.IR https://tldp.org/HOWTO/SCSI-Generic-HOWTO .
.PP
For Linux kernels before version 2.2.7 the size of the buffer is only 32KB.
This works, but for many cheaper scanners this causes scanning to be slower by
@@ -299,7 +299,7 @@ of the form ``restart (ncr dead ?)'' in your
.I /var/log/messages
file or on the system console, it's an indication that the timeout is too short.
In this case, find the line ``if (np->latetime>10)'' in file
-.I ncr53c8xx.
+.I ncr53c8xx.c
(normally in directory
.IR /usr/src/linux/drivers/scsi )
and change the constant 10 to, say, 60 (one minute).
@@ -329,7 +329,7 @@ and with target-id 0 would be called
.IR /dev/sg0a ,
and the device with target-id 1 on that same bus would be
called
-.IR /dev/sg0b,
+.IR /dev/sg0b ,
and so on.
.SH ENVIRONMENT