Sun has long set and as my work for today nears its end, i'll try to
write down all questions i have for now.
On Wed, 2008-11-05 at 05:20 -0800, Jack McGill wrote:
I'm just guessing here, but the mustek_usb2 backend probably doesn't
need a .conf file because it only supports one scanner at the
m. allan noah kitno455 at gmail.com writes:
On Wed, Nov 5, 2008 at 8:42 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Sanity is not the problem. The extreme need to make a release, coupled
with limited developer resources is the problem. Lets bump the
Hi everyone,
I have this ancient Canoscan D646U scanner.
According to the documentation, and my personal experience, it's
completely unsupported by the Sane drivers.
Now, I think it would be a waste to get a new scanner, this one produces
fine results, but I would like to get rid of running a
m. allan noah kitno455 at gmail.com writes:
On Wed, Nov 5, 2008 at 6:44 PM, Olaf Meeuwissen
olaf.meeuwissen at avasys.jp wrote:
m. allan noah kitno455 at gmail.com writes:
On Wed, Nov 5, 2008 at 8:42 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Le Thursday 06 November 2008 03:14:28 Olaf Meeuwissen, vous avez ?crit?:
...
They can't use these version 2 backends if they're stuck with a
version 1 frontend. Hence the need for support for a scenario where
you have both version 1 and version 2 backends installed.
Hello,
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
Hi,
The mixed version installations is something that distribution will
care about. A lot. Any distribution people hanging around that want
to chime in here?
/me raises both hands
Oh, wait.
JB.
--
Julien BLACHE
stef stef.dev at free.fr wrote:
to define a way both version can coexist we have to knowwhat
are the cases
which lead to this coexistence on a system. In my -possibly simplistic- view,
since any out of tree backend only needs a mere recompile to get in sync, I
don't see at
Contact!
Looks like in the end there was mistake on my end, that didn't let sane
detect my scanner. You see, with my distribution two packages are
shipped: sane-backends and sane-backends-libs. Before installing sane
from sources i did remove sane-backends but didn't do the same with
On Thu, Nov 6, 2008 at 5:01 AM, Julien BLACHE jb at jblache.org wrote:
stef stef.dev at free.fr wrote:
to define a way both version can coexist we have to knowwhat
are the cases
which lead to this coexistence on a system. In my -possibly simplistic- view,
since any out of tree
m. allan noah kitno455 at gmail.com wrote:
samsung MFP backend. No sources. No maintainer. No hope for an update
anytime soon. Shitload of users.
what do its soname symlinks look like?
:/usr/lib/sane% ls *mfp*
libsane-smfp.so.1 libsane-smfp.so.1.0.1
JB.
--
Julien BLACHE
On Thu, Nov 6, 2008 at 9:01 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Hi,
but no plain .so symlink?
Let me check the installer. I installed this one by cracking the
installer open, binary-patching the backend so it won't
segfault if not run by
Great news Igor,
You are making progress! At this point, I have a couple of suggestions.
1. Read up on doing a USB sniff with the scanner connected to a windows
machine. http://benoit.papillault.free.fr/usbsnoop/doc.php.en is the one that I
recommend. You can scan a very small object at low
m. allan noah kitno455 at gmail.com wrote:
ok, so if dll backend just tries to open [backendname].so, and ignores
Uh. Don't do that.
JB.
--
Julien BLACHE http://www.jblache.org
jb at jblache.org GPG KeyID 0xF5D65169
On Thu, Nov 6, 2008 at 10:16 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
ok, so if dll backend just tries to open [backendname].so, and ignores
Uh. Don't do that.
What is the point of the plain .so name if you can't use it?
allan
--
The truth is
m. allan noah kitno455 at gmail.com wrote:
What is the point of the plain .so name if you can't use it?
Linking against a specific backend, loading a specific backend from
the frontend directly, etc.
And what's the point in having versionned backends if you discard
the version?
Make the dll
On Thu, Nov 6, 2008 at 10:35 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
What is the point of the plain .so name if you can't use it?
Linking against a specific backend, loading a specific backend from
the frontend directly, etc.
And what's the
Sorry for jumping into the discussion but why don't we use
sane_get_option_descriptor() / sane_control_option() on a new
predefined option, for example, sane-version-features, which could
be read by a frontend and if, no error occured, set to required SANE
API level (aka. additional features
m. allan noah kitno455 at gmail.com wrote:
Please, describe for us how adding a new function to v2 backends is
going to make it easier for v1 and v2 backends to be installed at the
same time.
Tweaks to dll are needed in both cases. Except in your case you're
again trying to take an easy route
On Thu, Nov 6, 2008 at 11:12 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Please, describe for us how adding a new function to v2 backends is
going to make it easier for v1 and v2 backends to be installed at the
same time.
Tweaks to dll are needed in
On Thu, Nov 6, 2008 at 11:09 AM, Ilia Sotnikov hostcc at gmail.com wrote:
Sorry for jumping into the discussion but why don't we use
sane_get_option_descriptor() / sane_control_option() on a new
predefined option, for example, sane-version-features, which could
be read by a frontend and if, no
m. allan noah kitno455 at gmail.com wrote:
Hi,
My biggest concerns are those raised by Olaf- how do the two versions
coexist. I will bet you that the solution we come up with will be
EXACTLY the same, whether we add your new function or not. So, i want
No, if we go and add an optional status
On Thu, Nov 6, 2008 at 12:13 PM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Hi,
My biggest concerns are those raised by Olaf- how do the two versions
coexist. I will bet you that the solution we come up with will be
EXACTLY the same, whether we add
Hello,
On Nov 6 08:44 Olaf Meeuwissen wrote (shortened):
- will a version 2 dll backend still load version 1 backends?
- can version 2 frontends use version 1 backends?
- will version 1 frontends do the right thing with all version 2
backends?
- can everyone find the right match
m. allan noah kitno455 at gmail.com wrote:
but- as you have said several times in this thread, what about
frontends that link to the backend, bypassing dll? They might get a
frame-type they have never heard of, all while the backend says it
follows major version 1, which the standard says
sorry julien, should have included list
On Thu, Nov 6, 2008 at 1:06 PM, m. allan noah kitno455 at gmail.com wrote:
On Thu, Nov 6, 2008 at 1:02 PM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
but- as you have said several times in this thread, what
I am having trouble accessing an epjitsu Fujitsu fi-60F at a remote site.
The scanner was plugged in yesterday, the host PC has not been rebooted,
and I would like to avoid doing that during business hours.
The host PC is Ubuntu 8.10 desktop, libsane-1.0.19-6ubuntu1:
$ scanimage -V
scanimage
On Thu, Nov 6, 2008 at 1:16 PM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
In fact, adding a function is worse that i first though. A recent
frontend could connect directly to an old backend, inspect the version
number just like the standard says, and
m. allan noah kitno455 at gmail.com wrote:
In fact, adding a function is worse that i first though. A recent
frontend could connect directly to an old backend, inspect the version
number just like the standard says, and then call sane_status(). Bam!
This never happens with our current design,
m. allan noah kitno455 at gmail.com wrote:
ok, so how can a front-end know that it has connected to a 1.0
backend, since the sane standard states that the minor and point
release number are completely under the control of the backend? You
want to make the minor number do exactly what the
m. allan noah wrote:
the firmware is loaded when you run scanimage, so a reboot
should not be required.
SANE_DEBUG_EPJITSU=15 scanimage -L 2fi60.log
and look thru that logfile.
Thanks.
What does 'could not open device: 11' signify?
$ SANE_DEBUG_EPJITSU=15 scanimage -L 2fi60.log
$ cat
On Thu, Nov 6, 2008 at 1:23 PM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
ok, so how can a front-end know that it has connected to a 1.0
backend, since the sane standard states that the minor and point
release number are completely under the control of
On Thu, Nov 6, 2008 at 1:29 PM, Jeff Kowalczyk jtk at yahoo.com wrote:
m. allan noah wrote:
the firmware is loaded when you run scanimage, so a reboot
should not be required.
SANE_DEBUG_EPJITSU=15 scanimage -L 2fi60.log
and look thru that logfile.
Thanks.
What does 'could not open
It appears that 'usermod -a -G scanner myuser' and logging back in isn't
sufficient for scanner access on this system:
$ SANE_DEBUG_EPJITSU=15 sudo scanimage -L 2fi60.log
device `epjitsu:libusb:005:004' is a FUJITSU fi-60F 0A06 scanner
On Thu, Nov 6, 2008 at 1:44 PM, Jeff Kowalczyk jtk at yahoo.com wrote:
It appears that 'usermod -a -G scanner myuser' and logging back in isn't
sufficient for scanner access on this system:
$ SANE_DEBUG_EPJITSU=15 sudo scanimage -L 2fi60.log
device `epjitsu:libusb:005:004' is a FUJITSU fi-60F
m. allan noah kitno455 at gmail.com wrote:
As long as older frontends don't have to care about running with a
newer lib, there's no reason to bump the major.
10 mails ago you chewed me out for not thinking about the ecosystem,
and now you mean to ignore half of it?
WTF??? I say older
On Thu, Nov 6, 2008 at 2:35 PM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
As long as older frontends don't have to care about running with a
newer lib, there's no reason to bump the major.
10 mails ago you chewed me out for not thinking about the
Le Thursday 06 November 2008 11:01:40 Julien BLACHE, vous avez ?crit?:
stef stef.dev at free.fr wrote:
to define a way both version can coexist we have to knowwhat
are the
cases which lead to this coexistence on a system. In my -possibly
simplistic- view, since any out of
37 matches
Mail list logo
