[sane-devel] epson2 updated again

2009-06-02 Thread Chris Bagwell
OK, I'm not exactly sure what is different from my last test but now latest update of git and I can network scan great with my Artisan 800. I just tried a hand full of resolutions and both flatbed and ADF. All looked visually fine. Thanks for your work on this! Now, I guess I should go off an

[sane-devel] epson2 updated, need testing

2009-06-02 Thread Alessandro Zummo
On Tue, 02 Jun 2009 13:13:21 +0200 Dominik Wnek wrote: > Scanning with PX700W: the scanner now works over the network - in > binary, greyscale, colour, in various resolutions. xsane shows DPIs up > to 2400. > > 1. Sometimes, xsane will show "I/O Error" - maybe 2 times out of 10. > Trying again w

[sane-devel] byteorder.h

2009-06-02 Thread Alessandro Zummo
On Mon, 01 Jun 2009 20:01:50 -0500 Chris Bagwell wrote: > If no one else gives it a go, I'll have a hand at updating the autoconf > macro. I've not much experience with cross platform locations of those > defines. > > I see in my Fedora 11 Linux box that alot of those duplicates are > define

[sane-devel] epson2 updated, need testing

2009-06-02 Thread Dominik Wnek
Dnia 2009-06-02, wto o godzinie 01:47 +0200, Alessandro Zummo pisze: > > Hello, > >I just committed a reorganization of the epson2 driver which > should also have fixed the recently reported networking problems. > > I'd appreciate if you can test it. > > Still in the pipeline: > >

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-02 Thread Alessandro Zummo
On Tue, 2 Jun 2009 06:43:18 +0200 stef wrote: > > > what will the front-end do with that info? just plow ahead and ignore > > > it? Thats not really a status, but more of a param of the image data. > > > I think if you want that info, it makes more sense to turn the last > > > frame member of san

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-06-02 Thread stef
Le lundi 1 juin 2009 22:13:00 Alessandro Zummo, vous avez ?crit : > On Mon, 1 Jun 2009 15:14:05 -0400 > > "m. allan noah" wrote: > > what will the front-end do with that info? just plow ahead and ignore > > it? Thats not really a status, but more of a param of the image data. > > I think if you wa

[sane-devel] byteorder.h

2009-06-02 Thread Alessandro Zummo
it seems the autoconf generated byteorder.h overrides functions defined in the usual includes, generating messages like this one: ../include/byteorder.h:32:1: warning: "htobe16" redefined In file included from /usr/include/sys/types.h:217, from /usr/include/sys/uio.h:24,