Skipped content of type multipart/alternative-------------- next part
--------------
A non-text attachment was scrubbed...
Name: find_start_lexmark1.pnm
Type: image/x-portable-anymap
Size: 5205 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060522/1a5c6241/find_start_lexmark1-0001.pnm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: find_start_lexmark2.pnm
Type: image/x-portable-anymap
Size: 5205 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060522/1a5c6241/find_start_lexmark2-0001.pnm
From [email protected] Wed May 24 10:18:51 2006
From: [email protected] (=?ISO-8859-1?Q?Mat=EDas_Eissler?=)
Date: Wed May 24 10:19:22 2006
Subject: [sane-devel] Snapscan 310 unimplemented features
Message-ID: <[email protected]>
Hello people,
I'd like to thank and congratulate everyone for such a great work with
sane and the snapscan backend, great piece of work!
I'm using an Agfa SnapScan 310 scanner, its working just fine. However,
its status shows 'good' rather than 'complete' in the support matrix at
sane-project site. I would like to know which features are still
unimplemented (or where to find this information if it's available) and if
there is any work in progress to implement missing functionality, otherwise
I'd be very happy to contribute.
Not that I'm really an expert in the field of scanners drivers
development, but I've been coding in c/c++ for some years now, and I think
I'm able to make my small contribution if welcome.
Please accept my apologies if this wasn't the right place to ask, but I
couldn't find a more suitable one,
Thanks in advance,
Matias Eissler
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060524/08d6f2c6/attachment.html
From [email protected] Wed May 24 10:18:36 2006
From: [email protected] (Johannes Meixner)
Date: Wed May 24 10:19:45 2006
Subject: [sane-devel] device file for "canon" backend in sane-backends 1.0.17
Message-ID: <[email protected]>
Hello,
we got a bug report from a customer:
https://bugzilla.novell.com/show_bug.cgi?id=177492
but we don't have a scanner which is supported by the "canon"
backend, therefore I ask here:
In sane-backends 1.0.17 /etc/sane.d/canon.conf is
-------------------------------------------------------------------
#canon.conf
/dev/scanner
#/dev/sg0
-------------------------------------------------------------------
This seems to force the canon backend to look only at /dev/scanner
to find one of its supported scanners because with
"SANE_DEBUG_SANEI_SCSI=128" there is only "/dev/scanner" shown:
-------------------------------------------------------------------
[sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed:
No such file or directory
No scanners were identified.
-------------------------------------------------------------------
To get auto-detection I changed /etc/sane.d/canon.conf to
-------------------------------------------------------------------
#canon.conf
#/dev/scanner
#/dev/sg0
-------------------------------------------------------------------
but this falls back to the above case (i.e. only "/dev/scanner").
It seems to work better with
-------------------------------------------------------------------
#canon.conf
#/dev/scanner
/dev/sg0
-------------------------------------------------------------------
because now it tests the device which is assigned to /dev/sg0
(which is no such scanner but a USB mass-storage on my system)
and with "SANE_DEBUG_SANEI_SCSI=128" I get:
----------------------------------------------------------------------
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg0 does
not look like a scanner
No scanners were identified.
----------------------------------------------------------------------
At least it doesn't crash if the device file is wrong.
Unfortunately something like
-------------------------------------------------------------------
#canon.conf
/dev/scanner
/dev/sg0
/dev/sg1
-------------------------------------------------------------------
does not work to get some kind of auto-detection because
the canon driver tests only the last device entry ("/dev/sg1"
in this case).
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: [email protected]
90409 Nuernberg, Germany WWW: http://www.suse.de/
