Re: [sane-devel] Disabling epson backend build

Alessandro Zummo writes: > On Sun, 13 Sep 2015 10:56:36 +0900 > Olaf Meeuwissen wrote: > >> A simpler way would be to tune the hard-coded lists of supported >> scanners (in backend/epson_usb.c) and modify the *.desc files to follow >> suit. Oh, I see that both

Re: [sane-devel] Disabling epson backend build

On Sun, 13 Sep 2015 10:56:36 +0900 Olaf Meeuwissen wrote: > A simpler way would be to tune the hard-coded lists of supported > scanners (in backend/epson_usb.c) and modify the *.desc files to follow > suit. Oh, I see that both backends use the *same* file and that it

Re: [sane-devel] Disabling epson backend build

On Sun, 13 Sep 2015 11:32:47 +0900 Olaf Meeuwissen wrote: > Is this one of those scanners that have the RGB components on different > scanlines (several lines apart, depending on the resolution used) or is > this simply an RGB vs BGR issue? IIRC, even the epson

Re: [sane-devel] Disabling epson backend build

Alessandro Zummo writes: > On Sat, 12 Sep 2015 20:15:57 +0900 > Olaf Meeuwissen wrote: > >> I don't know what the various distribution do to the dll.conf file that >> their packages install, but since the epson backend has been disabled by >> default for five releases

Re: [sane-devel] Disabling epson backend build

m. allan noah writes: > I looked at the epson code- it appears that it will accept 'usb 0xVID > 0xPID' instead of just 'usb' in its config file. It does but only one such entry is supported. > I propose that we change the default epson config file to list the > Perfection 610's usb id, and any

Re: [sane-devel] Disabling epson backend build

Alessandro Zummo writes: > On Sat, 12 Sep 2015 09:25:37 -0400 > "m. allan noah" wrote: > >> I agree that there cannot be many, but you refused to investigate in >> that bug report. Given that the epson backend does seem to support the >> scanner, and the code is already in

Re: [sane-devel] Disabling epson backend build

On Sat, 12 Sep 2015 09:25:37 -0400 "m. allan noah" wrote: > I agree that there cannot be many, but you refused to investigate in > that bug report. Given that the epson backend does seem to support the > scanner, and the code is already in SANE, we should try to use it, >

[sane-devel] Disabling epson backend build

Hi Alessandro, AFAICS, the epson2 backend claims to support all devices that are supported by the epson backend. To avoid confusing users, the latter backend has been disabled in the dll.conf file since 2009-03-05. That corresponds to version 1.0.20. I don't know what the various distribution

Re: [sane-devel] Disabling epson backend build

On Sat, 12 Sep 2015 20:15:57 +0900 Olaf Meeuwissen wrote: > I don't know what the various distribution do to the dll.conf file that > their packages install, but since the epson backend has been disabled by > default for five releases I was thinking to disable the

Re: [sane-devel] Disabling epson backend build

I looked at the epson code- it appears that it will accept 'usb 0xVID 0xPID' instead of just 'usb' in its config file. I propose that we change the default epson config file to list the Perfection 610's usb id, and any other ids that we know epson2 wont support. Then we need to blacklist those ids

Re: [sane-devel] Disabling epson backend build

On Sat, 12 Sep 2015 08:59:08 -0400 "m. allan noah" wrote: > I looked at the epson code- it appears that it will accept 'usb 0xVID > 0xPID' instead of just 'usb' in its config file. I propose that we > change the default epson config file to list the Perfection 610's usb > id,

Re: [sane-devel] Disabling epson backend build

I agree that there cannot be many, but you refused to investigate in that bug report. Given that the epson backend does seem to support the scanner, and the code is already in SANE, we should try to use it, instead of turning users away. allan On Sat, Sep 12, 2015 at 9:11 AM, Alessandro Zummo