On Mon, Dec 08, 2003, David Brownell <[EMAIL PROTECTED]> wrote: > Herbert Xu wrote: > > > The problem here is the khubd is stuck in usb_set_address() waiting > > for the URB to complete, but it never finishes because the UHCI driver > > isn't getting any interrupts. > > OHCI could have the same problem. > > EHCI doesn't, since it's had a timer interrupt ever since it > first needed one to work on a VIA VT6202 chip ... :) > > I've thought that OHCI could detect this "IRQs are broken" > problem earlier. I suspect UHCI could use the same kind of > fix that came to mind: as the HCD starts, enable an IRQ > for SOF, and wait a couple milliseconds to make sure it > had a chance to arrive. If it came -- continue. Else, > report IRQs not working (because of ACPI or whatever) and > refuse to initialize that controller.
I've thought of doing something similar, but I decided against implementing it. Mostly because it would slow down the initialization of the controller and it will be obvious that something is broken when a device is plugged in later. Thinking about it now, I guess a clearer error message, for a problem as frequest as this, would be a good thing. JE ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
