There does seem to be a welcome flurry of activity relating to the snapscan
backend. It seems that the best method of bringing the software up to date
may be to assemble a core group of people with a variety of scanners and
have them test changes as proposed. I have the Agfa Snapscan 1212u_2
available for testing and would be willing to download CVS versions as
required
to verify operation on this scanner. I am not comfortable enough with the
backend
to understand the ramifications of all the changes, but have enough
debugging skills
to track down some problems. Steve, as you wrote some of the latest changes,
I would suggest you may be a good person to submit patches to the CVS or the
group of testers and have them report the results.
There seems to be quite a range of scanners that use the snapscan backend...
what
would be the best way to assemble a group of testers? additions to the
readme in
the CVS? this news group? Tagging related info with [snapscan] on this group
is definitely helpful in tracking related messages.
=======================================================
Lawrence Glaister VE7IT email: lg@jfm.bc.ca
1462 Madrona Drive http://jfm.bc.ca
Nanoose Bay BC Canada
V9P 9C9
=======================================================
----- Original Message -----
From: Steve Underwood <steveu@coppice.org>
To: <sane-devel@mostang.com>
Sent: Sunday, October 08, 2000 7:09 AM
Subject: Re: [SnapScan] color problem 300dpi
> Sebastien Sable wrote:
>
> > I do realize that it's difficult to maintain a backend when you don't
> > have a documentation and/or different scanners (indeed, i had to
> > compare each scsi command between the win driver and sane's one to
> > find my little bug, so it would not have been possible for someone
> > without this model). And I really appreciate what you and others
> > before have done to make snapscan backend work with each model.
> >
> > I will try to investigate the EAGAIN bug by my side and make useful
> > bug reports ;)
> > If you have any suggestion or want to try something, don't hesitate to
> > contact me; I have quite a good knowledge of the code with all I tried
> > to make it work.
>
> We seem to have received a few useful fixes for the SnapScan backend on
this
> list recently. Are they making it in to CVS? Is someone needed to
coordinate
> these fixes into a coherent, released whole? If certainly don't mind doing
that
> much, even if I am reluctant to become maintainer of things I am unable to
test.
>
> Regards,
> Steve
>
>
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sun Oct 08 2000 - 13:56:15 PDT