On Wed, 27 Apr 2005, David Brownell wrote: > > > Calling remove() and probe() ought to work just fine, and after all > > > those methods will always be well debugged. There was just a little > > > bitty self-deadlock problem in the PM core to fix ... > > > > Has that been fixed yet? Didn't Paulus submit something addressing this > > deadlock? > > Something. That's why I said "ought" and "was". I've not made > time to test that; it's the sort of interaction that tends to > break with all the stuff that's been changing in pmcore and in > the driver core. (Worth converting ASAP if it does indeed work.)
Maybe I'll give it a try... > > > Note that both EHCI and OHCI already _have_ such logic in the hub_status > > > code ... but it wasn't sufficient before. There are a LOT of paths > > > through > > > usbcore and HCDs on which things will trip up. > > > > Guess I'm used to UHCI, where things are simpler. > > I'm not sure it's a case of things being simpler. I was testing a > few dozen different configurations, and not all of them had those > wierd cases. There's nothing fundamentally different about UHCI; > it could have those same configurations. Can you remember any particular configurations or code paths that were troublesome? If similar things exist in UHCI then I need to know about them. As far as I'm aware there are no outstanding problems of this sort. Alan Stern ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
