-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
scar @ 03/23/2010 12:34 PM:
> linux packages mustek
> provides[1]?
> [snip]
>
> if i installed it, i would have to use --force-architecture.
so, as long as i don't have anything else installed, their driver
works... only on the command line with s
sc: not available
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100326/d08999d7/attachment-0001.bin>
> btw, isn't sane-backends licensed under GPL? ?how can mustek provide a
> package without the source?
Clearly, a vendor can ship a clean-room proprietary sane backend, as
there are no restrictions on the implementation of the sane standard.
However, this particular case is more of a gray area:
Hi!
It's recommended to write a test application while implementing support for
new hardware in SANE, because it's much easier to debug then library.
Can anyone give a link to such application?
And how can I force sane applications to use libraries in /usr/local (modified)
instead of system ones
Le vendredi 26 mars 2010 13:47:17 Yevgeny Gromov, vous avez ?crit :
> Hi!
> It's recommended to write a test application while implementing support for
> new hardware in SANE, because it's much easier to debug then library.
> Can anyone give a link to such application?
>
> And how can I force sane
Hi all,
One thing I've noticed developing simple-scan is a lot of the SANE
backends implement the same functionality. For example managing the
table of options. It would be nice if there was a generic sane driver
that the others could derive from, e.g.
static SANEGenericDriver *driver;
stat
2010/3/26 St?phane Blondon :
> 2010/3/26 m. allan noah :
>> Try getting a usb sniffer log of a low resolution small scan, using this
>> tool:
>>
>
>
> The attachment file is an archive; it contains two files:
> - a scan of a small area (10*10 pixels) at the lowest resolution
> available in the eps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ille @ 03/26/2010 02:10 AM:
> Le Thu, 25 Mar 2010 23:39:17 -0700,
> scar a ?crit :
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> scar @ 03/23/2010 12:34 PM:
>>> surely there is something we can learn from the linux packages
>>> must
Le Thu, 25 Mar 2010 23:39:17 -0700,
scar a ?crit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> scar @ 03/23/2010 12:34 PM:
> > surely there is something we can learn from the linux packages
> > mustek provides[1]?
>
> actually, i am surprised to find that these drivers actually work
On Fri, Mar 26, 2010 at 8:47 AM, Yevgeny Gromov
wrote:
> Hi!
> It's recommended to write a test application while implementing support for
> new hardware in SANE, because it's much easier to debug then library.
> Can anyone give a link to such application?
I usually just start with one of the li
Le jeudi 25 mars 2010 19:30:55 m. allan noah, vous avez ?crit :
> Some links:
>
> http://www.sane-project.org/lists/sane-backends-cvs.html#S-UNSUPPORTED
>
> which shows (among others)
>
> http://www.sane-project.org/unsupported/canon-4200f.html
> http://www.sane-project.org/unsupported/canon-500
On Fri, Mar 26, 2010 at 9:28 AM, Alejandro Imass wrote:
> 2010/3/26 m. allan noah :
>> Try getting a usb sniffer log of a low resolution small scan, using this
>> tool:
>>
>> http://www.pcausa.com/Utilities/UsbSnoop/
>>
>> Then we can see if it looks anything like the epjitsu machines.
>>
>
> Whi
Le vendredi 26 mars 2010 03:06:53 m. allan noah, vous avez ?crit :
> Our info indicates that this (and many other) Visioneer machines are
> RTS8801 chipset. Sane has an RTS8891 backend, it might be possible to
> modify that to work with the older chipset. Not sure if it is worth
> the time, reverse
2010/3/26 m. allan noah :
> Try getting a usb sniffer log of a low resolution small scan, using this tool:
>
> http://www.pcausa.com/Utilities/UsbSnoop/
>
> Then we can see if it looks anything like the epjitsu machines.
>
While St?phane captures de usb snoop,...
I think you said once tha these c
> ? ? ? ?Hello,
>
> ? ? ? ?I think it is easier to tell the exact genesys ASIC from the output of
> the
> latest version of sane-find-scanner. Or at least the full lsusb -v output.
Yeah- but I wrote the detection code for the later chips based on a
couple of rough guesses :)
allan
--
"The truth
2010/3/24 m. allan noah :
> At that point, I would investigate the epjitsu sane backend, as it
> already supports an epson chipset which may be related to the one in
> the V100.
>
epjitsu.conf.in explains that the driver needs a firmware called
'*.nal', often in a cab file. I didn't found such a f
16 matches
Mail list logo
