David: I've been thinking about state transitions for the UHCI driver, and I've got a few questions...
Is it true that the various callbacks emanating from hcd-pci.c have guaranteed mutual exclusion? When the driver detects that the controller has stopped functioning (like those pesky VIA units are prone to do) should it call usb_hc_died()? If yes, is there some notion that in the future hcd_panic() will eventually try to re-initialize the controller, up to some fixed number of retries (or retries within some fixed period of time)? Who really owns hcd->state? Some of the routines in hcd-pci.c set it while others expect the HCD to set it. It's not protected by any lock. Doesn't this need to be sorted out? Alan Stern P.S.: Those PCI cards you sent for testing arrived safe & sound. I haven't had any time to try installing them yet. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
