On Fri, 20 Oct 2006, Greg KH wrote: > > I see similar things. It must be caused by delays in the driver-model > > core. I have no idea why it should take more than 2 seconds to probe a > > newly-attached device. > > Huh? The driver core operates with no sleeps and runs in the process > that it was called in, so I don't think it would be sleeping 2 seconds. > > But enable debugging in the driver core (it's a config option) and see > what the timestamps tell you (enable the printk timestamp option, it's > very useful for stuff like this.)
I tried that. It wasn't the driver core causing the delay after all. Maybe it was something in usbhid... I don't know and I didn't try to trace it any farther. 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
