On Thu, 25 Mar 2004, David Brownell wrote:
> This should resolve the some of the issues reported on this thread,
> and I think it includes one of the changes you said did improve
> behavior with your scanner. I've been running with almost the same
> code for some months now, except for the usbfs changes that make
> it (finally!) reasonable to issue SET_CONFIGURATION.
>
> - Dave
This part of your patch, from proc_setconfig:
+ /* Don't touch the device if any interfaces are claimed.
+ * It could interfere with other drivers' operations, and if
+ * an interface is claimed by usbfs it could easily deadlock.
+ */
+ if (actconfig) {
+ int i;
+
+ for (i = 0; i < actconfig->desc.bNumInterfaces; ++i) {
+ if (usb_interface_claimed(actconfig->interface[i])) {
+ status = -EBUSY;
+ break;
+ }
+ }
+ }
will break gphoto2. It gets unhappy when the SETCONFIGURATION call
fails. The compromise I adopted that worked was to leave out that test
when calling usb_reset_configuration. See
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=108006210705499&w=2
Alan Stern
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
