On Thu, 20 Jan 2005, David Brownell wrote:
> I think those 2.6.11 changes can all be characterized as > streamlining the HCD glue, which will make adding new HCDs > easier in the future. Most of the 2.4.11 changes are ones > that should trigger compile time errors with older code. > So prepping a version to submit for 2.6.11 (please do!) > should be easy, and most patches for one version should > apply to the other. I have kept an eye on the hcd glue changes and they are indeed easy to incorporate. The problem is that the driver is still buggy. OK, I will post the problem soon. > > I have seen this particular error a lot. Mostly with timed > > plug-upplug cycles. I have tried to chase down the cause, > > but failed thus far. > > When you get the first IRQ, there's a flag to be set ... that's > just a warning to catch IRQ misconfiguration, very common on PCs > and something the USB developers can't help with. You must not > be setting that flag. I am just wondering, why in 2.6.10 no other hcd than sl811-hcd touches saw_irq? Olav ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel