From 9307c5837d3e02b2faff3f6ad54c36c02d3d171f Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Tue, 1 Nov 2005 21:07:25 +0000 Subject: [PATCH] Updated information about USB scanners. --- ChangeLog | 1 + README.freebsd | 28 +++++++++++++++------------- 2 files changed, 16 insertions(+), 13 deletions(-) diff --git a/ChangeLog b/ChangeLog index f8e438f66..d156bf852 100644 --- a/ChangeLog +++ b/ChangeLog @@ -3,6 +3,7 @@ * sanei/sanei_usb.c: Added support for detecting vendor and product id with FreeBSD kernel scanner driver (based on patch in FreeBSD ports). + * README.freebsd: Updated information about USB scanners. 2005-10-31 Oliver Schwartz diff --git a/README.freebsd b/README.freebsd index c0e8006cb..d3423c2c9 100644 --- a/README.freebsd +++ b/README.freebsd @@ -15,22 +15,24 @@ USB-scanners: USB-Scanners are supported by FreeBSD. The USB scanner driver "uscanner" and access over libusb can be used. -To get your scanner detected by the uscanner driver, it may be necessary to -add its vendor and device ids to the kernel and recompile. Use MAKEDEV to -generate the /dev/uscanner* files if they are not already there. Use -sane-find-scanner to find your scanner and edit your backend's configuration -file appropriately. +For some backends (e.g. gt68xx) you MUST use libusb. The uscanner driver won't +work because it doesn't support control messages or interrupt endpoints. -If you want to use libusb, your scanner should *not* be claimed by the -uscanner driver. Make sure, that /dev/ugen* and /dev/usb* devices are -available. Use /dev/MAKEDEV to create them, if necessary. +If you want to use libusb, your scanner should *not* be claimed by the uscanner +driver. Make sure, that /dev/ugen* and /dev/usb* devices are available. Use +/dev/MAKEDEV to create them, if necessary. Make sure that the user has write +access to the appropriate device files. -For some backends you must use libusb. The uscanner driver won't work because -automatic detection, control messages, or interrupt endpoints are needed. +To get your scanner detected by the uscanner driver, it may be necessary to add +its vendor and device ids to the kernel and recompile. Use MAKEDEV to generate +the /dev/uscanner* files if they are not already there. Use sane-find-scanner to +find your scanner. scanimage -L should find it automatically. Make sure that the +user has read access to /dev/usb* and read and write access to /dev/uscanner*. Parport-scanners: ----------------- -I don't have much information about these. The Mustek 600 II N scanner seems to work, others may or may not work. Please contact me or the SANE mailing -list if you succeeded in using a parport scanner. +I don't have much information about these. The Mustek 600 II N scanner seems to +work, others may or may not work. Please contact me or the SANE mailing list if +you succeeded in using a parport scanner. -2002-07-14 Henning Meier-Geinitz +2005-11-01 Henning Meier-Geinitz