On Wednesday 19 January 2005 12:13 am, Oliver Neukum wrote: > Am Dienstag, 18. Januar 2005 20:59 schrieb David Brownell: > > It's possible that some PCMCIA changes affected this too. �I seem > > to recall thinking that the cardbus/pcmcia logic should have been > > notifying the OHCI code about the disconnect before the IRQ logic > > saw it ... and I wouldn't swear that things would behave quite > > right if someone _did_ fix that problem. �(Though in that case > > it'd be more equivalent to "rmmod ohci-hcd" with live devices.) > > That is asking too much of the cardbus logic. It would need to > process a removal event instantaneously to meet that requirement > as an interrupt can happen any time.
The problem I was referring to was that the cardbus logic wasn't _ever_ reporting a device unplug before some interrupt arrived. I can't see that asking for such a thing is too much, especially in clean cases like "cardctl eject". - Dave ------------------------------------------------------- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
