Messages in this thread | | | From | Duncan Sands <> | Subject | Re: [linux-usb-devel] Re: [OOPS, usbcore, releaseintf] 2.6.0-test10-mm1 | Date | Thu, 11 Dec 2003 10:21:05 +0100 |
| |
On Wednesday 10 December 2003 20:43, David Brownell wrote: > Duncan Sands wrote: > > On Wednesday 10 December 2003 18:34, David Brownell wrote: > >>>Unfortunately, usb_physical_reset_device calls usb_set_configuration > >>>which takes dev->serialize. > >> > >>Not since late August it doesn't ... > > > > In current 2.5 bitkeeper it does. > > usb_physical_reset_device() does not call usb_set_configuration() > except in the known-broken (for other reasons too!) "firmware changed" > path. Known-broken, but not yet removed since nobody has reported > running into that or the other deadlock; the real fix is force > re-enumeration of the device.
Still, it could be changed into a call to usb_physical_set_configuration while we're waiting for a real fix, right?
Ciao,
Duncan. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |