On Fri, 20 Oct 2006, David Brownell wrote: > > I'll have to take a look at this over the weekend. I don't remember > > seeing anything like it in previous testing with OHCI, but I wasn't > > running 2.6.19-rc2 at the time. > > You might not have tested with usbfs either ... or have noticed that > glitch with the strange address assignments.
I forgot to address this in the previous message... The strange address assignments weren't a glitch at all. Your log shows clearly that the address was originally set to 2, and it didn't get changed to 3 until after the logical disconnect and re-enumeration. That's exactly how it's supposed to behave. The very same mechanism would apply, for example, after a port reset following a firmware update. Seeing that the descriptors had changed, the hub driver would initiate a logical disconnect and then re-enumerate as though a new device were present -- which in some sense it would be. I haven't tried using usbfs, but I did try unloading the test device's driver and then reloading it, which has pretty much the same effect: an autosuspend followed by an autoresume. With that new patch there was no trouble. Alan Stern ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
