[sane-devel] Third revision of Scanner HOWTO available

[Henning Meier-Geinitz]

Hi,

On Sat, Jul 19, 2003 at 04:45:12PM -0500, Howard Shane wrote:
> ...at http://66.25.191.66/docs/HOWTOS/Scanner/index.html
> 
> This is your last chance to point out any remaining technical errata
> prior to grammatical review and (hopefully) publication by TLDP.

Ok, lets see if I can nitpick a bit :-) I'm not a native english
speaker, so grammar/spelling corrections may be wrong.

| 1. Introduction
| 
| within X-windows

->"The X Consortium requests that the following names be used when
   referring to this software: X, X Window System, X Version 11, X Window
   System, Version 11, X11" (from man X)

| It does not address how use the available software 

--> how to use (?)

| 2.1. SCSI Devices
| While most SCSI-cards that linux supports allow scanning, you should
| be aware that if your SCSI card came come bundled with your scanner
| you may run into problems, as these may not be complete SCSI cards
| (much like a winmodem). 

I don't think that's a very good comparison. While a winmodem is not a
modem at all (it's more a sound chip), the bundled SCSI adapter are
real SCSI cards. They may not be of good qquality, i.e. don't have
IRQ/DMA support. But at least the ones I know of can be used for e.g.
CDROMS, too. Well, I wouldn't do that but anyway.

| 3.1. USB Scanners and Libusb

| $ grep -e USB_DEVICEFS /boot/config-X.XX

--> I think it's easier to do
grep "\(usbfs\)\|\(usbdevfs\)" /proc/filesystems

This way you are checking the currently running kernel.

| If you have USB device filesystem running, and you have usb devices
| loaded already you can confirm this with cat /proc/bus/usb, which
| should give you a list of active devices the kernel is aware of.

--> It's "cat /proc/bus/usb/devices".

| IMPORTANT: You cannot have both kernel scanner support enabled (i.e.,
| compiled in statically or the module loaded if a module) and libusb
| installed and access the hardware at the same time, or nothing will
| work.

Well, I know what you mean but it's not completely true the way you
have written it.

If the scanner driver is loaded and has detected the scanner it will
"lock" it. So libusb can't use it. But the scanner driver can still
use it. After unloading the scanner driver, libusb can use it again.

So there is no real conflict. The scanner driver just has the higher
priority.

| (A hint for newbies: [...]
| where 'file.txt' will contain the info that can then be accessed with
| cat.)

--> with "less", otherwse it will scroll again too fast.

| 3.2.2. Kernel USB Support

| USB-ohci, USB-ehci,

--> lower case (usb-ohci)

| 3.3.2. Directio
| 
| Some parallel port scanners can be accessed with directio (a.k.a.
| direct_IO) instead; you will likely need to compile your own SANE
| binaries and have libieee1484 installed. You will need generic scsi
| device support in your kernel. At compile time use the
| --enable-parport-directio --enable-scsi-directio with the ./configure
| script.

I'm not an expert in these things but I think you are mixing different
topics here.

--enable-parport-directio means, that direct hardware access to the
ports (inb/outb assembler commands) is used. So you don't need
libieee1284 (not 1448) here. This is only used in the mustek_pp and
umax_pp backends.

--enable-scsi-directio