Re: [sane-devel] Ricoh IS410

> I now have three other scanners, which work, including my scsi Microtek > Scanmaker e3, which is on the same scsi bus as my Ricoh IS410. I still > would like to get it going, if you're game. I started from scratch, using > your latest tarball, which was dated February 2015. It seems to be >

Re: [sane-devel] [PATCH 1/2] add PNG format to scanimage

2015-09-12 9:13 GMT+02:00 Olaf Meeuwissen : > Hi Matteo, > > Thanks for taking the trouble to add optional PNG and JPEG output > support! > > I've done a quick review of both patches and there are a few things that > I'd like to point out: > > - Why do you let users

[sane-devel] [PATCH v2 1/2] add PNG format to scanimage

--- write help and manpage acinclude.m4 | 13 + configure.in | 1 + doc/scanimage.man| 4 +- frontend/Makefile.am | 2 +- frontend/scanimage.c | 143 ++- 5 files changed, 148 insertions(+), 15 deletions(-) diff --git

[sane-devel] [PATCH v2 2/2] add JPEG support to scanimage

--- write help and manpage doc/scanimage.man| 4 +- frontend/Makefile.am | 2 +- frontend/scanimage.c | 103 +-- 3 files changed, 103 insertions(+), 6 deletions(-) diff --git a/doc/scanimage.man b/doc/scanimage.man index 387e962..480d51e

Re: [sane-devel] ioperm or portaccess for qcam

Luiz Angelo Daros de Luca writes: > Hello, > > While trying to solve a problem with missing inb/outb for mips, I saw this > check in configure: > > qcam) > if test "${ac_cv_func_ioperm}" = "no" \ > && test "${ac_cv_func__portaccess}" = "no"; then > echo "*** $be backend

[sane-devel] [PATCH v2 1/2] use getopt

Implement command line parsing using getopt, replace the help string with a nicer one. --- set proper return value with invalid arguments make arguments to -a -d and -s optional frontend/saned.c | 90 ++-- 1 file changed, 48 insertions(+), 42

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] Preparing for a sane-backends release

Hi Dieter, Dr.-Ing. Dieter Jurzitza writes: > Hi Olaf, >> * >> Me wonders too. I haven't seen one this century. I even wonder if SCSI >> scanners still need to be supported. >> * > happily using my HP6300C through the SCSI bus with sane ... I do not know how > many people like me are

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

[sane-devel] [PATCH v2 2/2] add option to bind address

add optional argument '-b' to let saned bind a specific address --- also bind the address if AF_INDEP add man and help documentation doc/saned.man| 29 - frontend/saned.c | 17 - 2 files changed, 32 insertions(+), 14 deletions(-) diff --git

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] [PATCH 2/2] add option to bind address

Hi Matteo, This also looks good but it is missing documentation for the option. Both in the usage message as well as the saned manual page. Could you fix that? Matteo Croce writes: > [snip] > @@ -3288,6 +3289,9 @@ main (int argc, char *argv[]) >run_mode = SANED_RUN_DEBUG; >

Re: [sane-devel] [PATCH 1/2] use getopt()

Hi Matteo, I reviewed this patch and it looks *mostly* okay. The only place where I think you dropped the ball a bit is in the command-line option error handling. The original code outputs a usage message when it finds the help option as well as when it encounters anything unexpected. It also

Re: [sane-devel] [PATCH 1/2] add PNG format to scanimage

Hi Matteo, Thanks for taking the trouble to add optional PNG and JPEG output support! I've done a quick review of both patches and there are a few things that I'd like to point out: - Why do you let users select PNG/JPEG outputs even when the support is not available when HAVE_LIBPNG and/or

Re: [sane-devel] Preparing for a sane-backends release

Hi Johannes, Johannes Meixner writes: > 1) > Right now I filed > https://alioth.debian.org/tracker/index.php?group_id=30186=410366 > with my fix-buffer-overflow.patch attached > that fixes a too small array in backend/niash.c This has been assigned. Stef, can you take a look? > 2) > My

Re: [sane-devel] [PATCH 1/2] use getopt()

Sorry about that, I'll fix in a new version, also what do you think about a nicer help string like: "Usage: %s [-a username] [-d n] [-s n] [-h]\n" The main issue is that it seems that under OS/2 the socket handle is passed as an extra argument, what to do? Handle the extra argument only if

Re: [sane-devel] [PATCH 2/2] add option to bind address

Yes will do, but I noticed that I have to use bind_addr even in do_bindings instead of INADDR_ANY, I have a newwer version of the patch 2015-09-12 8:58 GMT+02:00 Olaf Meeuwissen : > Hi Matteo, > > This also looks good but it is missing documentation for the option. >

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, >

Re: [sane-devel] [SOLVED] Re: plustek backend failing to open device under non-root

The udevadm program can be very useful when one wants to develop rules and diagnose udev issues. I have found "udevadm --debug test ..." particularly useful when I suspect some rule other than the one I intend has handled a udev event. -- sane-devel mailing list:

Re: [sane-devel] Preparing for a sane-backends release

Hi Olaf, > * > Me wonders too. I haven't seen one this century. I even wonder if SCSI > scanners still need to be supported. > * happily using my HP6300C through the SCSI bus with sane ... I do not know how many people like me are "out in the wild", but I am glad to have sane support

[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] [PATCH 0/3] magicolor 4690MF support

On Sat, Sep 12, 2015 at 8:36 AM, Olaf Meeuwissen wrote: > Hi, Hi, [snip] > I only have some concerns about the "FIXME" for the network OID. Can > the device be used over the network with this value? If no, then the > network interface should probably be removed

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