On Wed, 7 Jul 2004, Greg KH wrote: > On Wed, Jul 07, 2004 at 02:54:16PM -0700, Greg KH wrote: > > On Tue, Jul 06, 2004 at 12:11:19PM -0400, Alan Stern wrote: > > > Greg: > > > > > > As Andrew Morton has already spotted, I messed up the interpretation of > > > the result codes from various _trylock() routines. I didn't notice that > > > down_trylock() and down_read_trylock() use opposite conventions for > > > indicating success! This patch fixes the incorrect interpretation of > > > down_trylock(). That error may well be responsible for some of the > > > problems cropping up recently with OHCI controllers. Please apply. > > > > Applied. > > > > But even with this patch, and Andrew's, I have a hang at boot with my > > USB mouse plugged in (uhci system). > > If I remove the mouse, and then boot, it works just fine. I can then > insert it and the drivers are loaded just fine too. > > Looks like a race on accessing usbfs and loading a driver at the same > time, as the "cold-boot" code scans usbfs to determine what driver to > load.
Our emails are a bit out of sync. Did patch as340 fix your problem? Never mind for now the philophical/design questions about the code; I'll discuss them separately. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
