summaryrefslogtreecommitdiff
path: root/backend/epjitsu.conf.in
diff options
context:
space:
mode:
Diffstat (limited to 'backend/epjitsu.conf.in')
-rw-r--r--backend/epjitsu.conf.in37
1 files changed, 37 insertions, 0 deletions
diff --git a/backend/epjitsu.conf.in b/backend/epjitsu.conf.in
new file mode 100644
index 0000000..cabe6b2
--- /dev/null
+++ b/backend/epjitsu.conf.in
@@ -0,0 +1,37 @@
+# For scanners connected via USB on a known device (kernel driver):
+#usb /dev/usb/scanner0
+
+# For scanners connected via USB using vendor and device ids (libusb):
+#usb VENDORID PRODUCTID
+
+# NOTE: if you have to add your device here- please send the id and model
+# to the author via email, so it can be included in next version. kitno455 at
+# gmail dot com - with epjitsu in the subject line
+
+# These devices require a firmware file in order to function, which must be
+# extracted from the Fujitsu Windows driver. Presumably the Mac versions
+# contain the firmware as well, but the author has no access such a machine.
+
+# Firmware is installed in several different locations by the fujitsu software,
+# using the windows 'search' feature to look for '*.nal' is the easiest way to
+# find them. They should be ~65K, and have the scanner's name as part of the
+# file name. They are often inside a .cab file.
+
+# Copy the file someplace sane can reach it. Then update the line below.
+# NOTE: the firmware line must occur BEFORE the usb line for your scanner
+
+# Fujitsu fi-60F
+firmware @DATADIR@/sane/epjitsu/60f_0A00.nal
+usb 0x04c5 0x10c7
+
+# Fujitsu S300
+firmware @DATADIR@/sane/epjitsu/300_0C00.nal
+usb 0x04c5 0x1156
+
+# Fujitsu S300M
+firmware @DATADIR@/sane/epjitsu/300M_0C00.nal
+usb 0x04c5 0x117f
+
+# Fujitsu S1300
+firmware @DATADIR@/sane/epjitsu/1300_0C26.nal
+usb 0x04c5 0x11ed