On Wednesday 05 January 2005 3:58 am, Pedro Venda wrote: > David Brownell wrote: > | > | OK, try this slightly modified version. Looks like > | the Intel chip sets the HALT bit then spontaneously > | clears it, while the ALI may never set it. > > this one has a different output, although I don't understand if it's working > properly since there are still some fatal errors... there isn't a fatal error > but a BOGUS error, as introduced by the patch.
That patch _reports_ that the hardware's error report (IRQ) is BOGUS. The original issue was that the driver wasn't noticing that the chip was misbehaving, and treated it like a real problem instead of an ignorable chip misbehavior. > EHCI 1.00, hcd state 1 instead of the old value 0 means that the driver's > working now? More like the _hardware_ is working, now that the driver knows enough to ignore that error IRQ in certain cases. The patch I submit won't actually print anything when it gets that "BOGUS" path ... there's nothing to be done with that IRQ except ignore it, and no point in potentially worrying end users or sysadmins. - 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
