[sane-devel] xerox_mfp usb malfunction

On Wed, Mar 9, 2011 at 11:46 AM, m. allan noah wrote: > 2011/3/9 Warren Turkal : > > 2011/3/9 ABC > > > What i think should actually happen is that sanei should have it's own > > method for dealing with usb (and other busses) in whatever form it takes > > (e.g. /dev/scanner dev file or libusb o

[sane-devel] xerox_mfp usb malfunction

2011/3/9 ABC > | for (tr = available_transports; tr->ttype; tr++) { > | > |DBG (4, "%s: %s: tr->ttype=%s\n", __FUNCTION__, devname, tr->ttype); > | > |if (!strncmp (devname, tr->ttype, strlen(tr->ttype)) || > |(!strncmp (devname, "libusb", strlen("libusb")) && > | !strnc

[sane-devel] xerox_mfp usb malfunction

2011/3/9 Warren Turkal : > 2011/3/9 ABC > ?What i think should actually happen is that sanei should have it's own > method for dealing with usb (and other busses) in whatever form it takes > (e.g. /dev/scanner dev file or libusb or scsi device or whatever). Sanei > should call any callbacks into

[sane-devel] xerox_mfp usb malfunction

On Tue, Mar 8, 2011 at 1:23 PM, m. allan noah wrote: > The author was responding to bug reports yesterday, so I think it's a > bit early for you to be pessimistic :) > This is a fair point. wt -- next part -- An HTML attachment was scrubbed... URL:

[sane-devel] xerox_mfp usb malfunction

I will correct the bug. Device string is parsed for network scanner support. On Tue, Mar 08, 2011 at 08:23:43AM -0500, m. allan noah wrote: > I am familiar with sanei_usb device detection, and I speak diff. The > only thing that seems odd is just why the backend is parsing the > device strings.

[sane-devel] xerox_mfp usb malfunction

I am familiar with sanei_usb device detection, and I speak diff. The only thing that seems odd is just why the backend is parsing the device strings. The author was responding to bug reports yesterday, so I think it's a bit early for you to be pessimistic :) allan -- "The truth is an offense, bu

[sane-devel] xerox_mfp usb malfunction

Responses below. On Tue, Mar 8, 2011 at 1:13 AM, m. allan noah wrote: > Thanks for the patch. I must confess I don't quite understand the > code. A lot of the lines of code just added debugging output so that I could see what functions were being called as I find the code pretty difficult to fol

[sane-devel] xerox_mfp usb malfunction

I have a small patch that works around a bug in the xerox_mfp driver. It is attached. The bug boils down to the following. The devname generated by the sanei code is "libusb" instead of "usb". I think that this may stop the xerox_mfp backend from working on any system using libusb to talk to a USB

[sane-devel] xerox_mfp usb malfunction

Thanks for the patch. I must confess I don't quite understand the code. If the caller provides a device name which does not exactly exist, I think the backend should just return an error, instead of trying to find a similarly named device. There is no guarantee that device names will have a consist