On Tue, 30 Mar 2004, Malcolm Blaney wrote: > After reading the uhci paper, I decided I couldn't do much more if the > controller isn't sending out an interrupt at all. So I tried to trace > back the call to uhci_irq(), which should happen if the controller is > reponding at all. I found that handle_IRQ_event() in irq.c does get > called after fsbr is set. Is it fair to assume that this interrupt is > the one that should get past along to uhci_irq()? (but isn't in this > case..)
It could be, if it's the IRQ line your UHCI controller uses. Note that other devices may share the same IRQ line, however, so that request might not come from the controller. > The computer hangs in some timing code not too far down the track, so > maybe this isn't (directly) a problem with usb? That's certainly possible. On the other hand, it's not clear why it should happen only when you have FSBR turned on. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
