Greg, Yes, I'm referring to 7-29. I don't have the source handy and my "information" is anecdotal. It might be a problem with a particular implementation that is not the "standard" USB package for Linux.
If you say it's there, I'll believe you. On the other hand, if some kind person would send me the source for hub.c I could check for myself. ;-) David Wooten > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf > Of Greg KH > Sent: Wednesday, February 13, 2002 10:59 AM > To: David Wooten > Cc: [EMAIL PROTECTED] > Subject: Re: [linux-usb-devel] FW: Connect Debounce > > > On Wed, Feb 13, 2002 at 10:42:46AM -0800, David Wooten wrote: > > I was recently informed that the USB driver doesn't allow > 100ms of debounce > > time after each connect event before it generates a USB bus > reset as is > > required by the USB specification. Is this true? > > Are you referring to Figure 7-29 in the spec? If not, what are you > referring to? > > If you look in the code for usb_reset_device() in hub.c, you > will see a > delay for just this event. > > Are you not seeing this on the wire? > > thanks, > > greg k-h > > _______________________________________________ > [EMAIL PROTECTED] > To unsubscribe, use the last form field at: > https://lists.sourceforge.net/lists/listinfo/linux-usb-devel > _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
