Hey stef, i'm really struggling to work out what all these frontend
writes are for. Below is a grep of the frontends from a scan, I have
done several scans and they all roughly follow this format. I'm not sure
why the offset (regs 05 - 07) have values 0x80 and 0xff and the values
for both
Le mercredi 27 janvier 2010 07:17:21 Andrey Loginov, vous avez ?crit :
As of previosu message currently I have successful calibration using
xsane.
I will also try to play with motors and other staff to make it better.
?
Hello,
nice to see it working. From the picture you
Le jeudi 28 janvier 2010 02:15:01 Chris Berry, vous avez ?crit :
Hey stef, i'm really struggling to work out what all these frontend
writes are for. Below is a grep of the frontends from a scan, I have
done several scans and they all roughly follow this format. I'm not sure
why the offset
No stef im almost certain this isnt a Wolfson, from an old project page
I think it is an Analog Digital 9826
Link:
http://www.analog.com/en/audiovideo-products/cameracamcorder-analog-front-ends/ad9826/products/product.html
I too am puzzled why there are so many writes to the frontend, the
Hi all,
On 26.01.2010, at 15:46, m. allan noah wrote:
Seems like an individual backend should not need to parse the device
string. Isn't there some other way to come up with a unique semaphore,
like process id?
the process id could be used, but it may fail theoretically. One
example is a
On Thu, Jan 28, 2010 at 6:51 AM, Oliver Schwartz Oliver.Schwartz at gmx.de
wrote:
Hi all,
On 26.01.2010, at 15:46, m. allan noah wrote:
Seems like an individual backend should not need to parse the device
string. Isn't there some other way to come up with a unique semaphore,
like process
.
Any clues appreciated.
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100128/7e377cd4/attachment.htm
/sane-devel/attachments/20100128/da60ac1b/attachment.htm
Hi all,
On 28.01.2010 at 14:39 m. allan noah wrote:
I would do both- process ID combined with a hash of the device name,
I believe that would defeat the purpose. The whole point of the mutex is to
protect the USB device from simultaneous access from two processes, e.g. the
reader process and
Already got the epkowa and related stuff installed. Debug does't provide more
clues either other than show the libs being loaded then closed. The only clue
I've seen so far is that Inappropriate ioctl error in my strace log.
What's really annoying, I had this epson v10 working on an old P2 box
--- On Thu, 1/28/10, Alesh Slovak alesh.slovak at avasys.jp wrote:
The plugin library can go wherever you want
as long as you specify where it is in epkowa.conf via the
interpreter line.
Ah it was a symlink prob, just needed to ln -s libesint66.so.2.0.1 libesint66.so
scanimage -L
device
11 matches
Mail list logo
