On Wednesday 05 January 2005 6:40 am, Christian Iversen wrote: > I've been running with this patch for some time now (well, at least 10 days), > and I haven't had any problems of any kind. USB just seems to work for me > now. Of course, that could be pure luck, but since David and I looked at > which changes have been going on in the ehci-driver, and the usb-core in > general at the revisions where it originally broke, we discovered that it > _no_ direct changes were made in the ehci-driver in the breaking revision. > > That suggests to me that the chip doesn't entirely work within specs, that > the > driver is good, and that we need this patch to catch a corner case that is > wrongly handled by the hardware. That could be wrong, of course, but that's > my view of the situation :)
While it's clear that both the ALI and Intel chips aren't acting according to spec -- that IRQ is only supposed to trigger as part of halting the controller!! -- it's probable that there's something Linux _could_ be doing differently, to avoid triggering that IRQ. And it's even possible that same "something" could be called a bug. Not that we have any ideas about what that "something" is, except that these bogus IRQs started to appear in 2.6.6 (or maybe 2.6.7). So I'll be submitting a patch for this problem. - Dave ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
