On Tue, 11 Jul 2006, Ajay Jain wrote: > > Remember the definitions of reset and suspend. Reset is an SE0 signal, > > which is the default bus state when no device is attached or the device's > > pull-up resistor hasn't been turned on. Suspend is a J signal, which is > > the default bus state when the device's pull-up resistor is on and the > > port is disabled. > > > > So when you see the bus go between reset and suspend, it means that the > > device is turning its pull-up resistor off and on. > > May be yes, but then I have a counter observation. When I use another > host I always see a reset - suspend - reset - get_device_descriptor - > reset - set_address sequence. This is something that I observe > invariably. When I use the old host, I always see reset - suspend - > reset - suspend - reset - suspend - reset - suspend - reset - > get_device_descriptor - reset - set_address sequence. The observations > on both these pc's is invariable. If it was a device oddity, then why > would it behave differently on two different hosts?
I don't know. Have you tried using any sort of USB sniffer program to monitor the host's requests to the bus's root hub? 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
