Greg KH wrote:
> Hm, but usb_hcd_irq() reports back the proper interrupt return value. I
> don't see how this could happen, unless the ehci driver was somehow
> halted...
>
> David, any ideas?
It's getting an IRQ before the driver expects them,
I suspect. I think the HCD glue needs a new entry,
forcing hardware reset before the rest of hcd init.
Easy/simple to do; and IMO reasonable too.
Of course, it's also strange that leaving ACPI on
causes problems at this level. And that it only
happens for EHCI.
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 15 2003 - 22:01:00 EST