://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100108/77c091f6/attachment.pgp
Thanks for the quick reply stef, hope you had a good christmas/new year :).
I have made changes to the GPIO settings as appropriate (i.e. matched
the settings to what I believe is correct from register writes) but I
could only find values for 0x6b, 0x6d, 0x6e and 0x6f. I couldn't find a
write
Leslie Jensen wrote:
I'm on a FreeBSD 8.0-RELEASE with an EPSON V500
I've installed:
epkowa-2.11.0_2 The sane-epkowa driver for FreeBSD
sane-backends-1.0.20_4 API for access to scanners, digitals camera,
frame grabbers
sane-frontends-1.0.14_5 Tools for access to scanners, digitals
Alessandro Zummo wrote:
On Sun, 3 Jan 2010 15:14:38 +0100
Rainer Dorsch rdorsch at web.de wrote:
Are these the areas in epson2.c you are refering to:
/*
* Make sure that the number of lines is correct for color shuffling:
* The shuffling alghorithm produces
Le vendredi 8 janvier 2010 04:38:07 Chris Berry, vous avez ?crit :
Thanks for the quick reply stef, hope you had a good christmas/new year :).
I have made changes to the GPIO settings as appropriate (i.e. matched
the settings to what I believe is correct from register writes) but I
could
On Fri, 08 Jan 2010 14:06:54 +0900
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
That code does the wrong thing. The epkowa backend fixed the
s.params-lines calculations in, eh, iscan-1.14.0 (released in 2005).
Search epkowa.c of a recent iscan for finalise the number of scanlines
to
Hello
I am trying to make Xerox Travel Scanner 100 portable scanner under
Ubunto 9.10(karmic).
When I use sane-find-scanner -v -v, it shows:
device descriptor of 0x04a7/0x04ac at 001:003 (Xerox Travel Scanner
100)
bLength 18
bDescriptorType 1
bcdUSB2.00
Hi,
I came across this while using gscan2pdf to scan a number of postcard-sized
sheets.
Because the format is unknown to gscan2pdf (and the underlying scanner
backend) at first I have entered the dimensions of the sheets manually.
The sheets are 105mm x 148mm in size.
My scanner is an
This happens because the backend does not pad your input values when
it sends them to the scanner. The sane standard does not specify
whether this is required or not. The avision backend author chose not
to. Many (if not most) other backends do make this correction. If you
are able to produce a
