The hub driver is inefficient about the way it checks hub/port statuses. Whenever a status interrupt message is received, it always checks _all_ the ports plus the hub itself. However, the status message contains a bitmask indicating exactly which ports (or hub) have pending status changes, and in principle we could use that information.
Is there any practical reason not to check just the ports (or hub) listed in the status interrupt message? Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
