On Fri, 23 Jan 2004, Axel Waggershauser wrote: > - with your patch the urb gets unlinked when the controller suspends, > that happens about a second after the unplugging.
So now that part works and your driver, even in its original form, doesn't cause a kernel panic. > - without your patch the urb gets unlinked after the replug. > > The result at the end seemed to be the same: my device did not enumerate > anymore. And this enumeration seemed to fail in a similar way than my > test program, there seems to be a pending urb that does not get removed > properly if the device gets unplugged again. I tried only a few times, > maybe there is some non-determinism involved here as well. Once the unplug stuff has finished and the disconnect processing is over, there should be no record of your device remaining within the kernel or the controller. When you replug, it should look and behave exactly the same as when you plugged it in the first time. That's why I wonder if the timeout during the enumeration isn't the fault of your device somehow. Of course, the timed-out URB should get dequeued when you unplug again. That should behave the same way as your driver's URB that gets dequeued the first time you unplug. Alan Stern ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
