On Wed, 28 Jul 2004, Duncan Sands wrote: > > That's right. But you might not have to go to all the trouble of using > > schedule_work(). If loading the firmware does change the device or > > configuration descriptors at all, then calling usb_reset_device() will be > > enough to start re-enumeration and reprobing. It would only be necessary > > to make sure that with the firmware loaded, the system selects > > configuration 2. > > But how to avoid an infinite loop if the hardware doesn't respond as you > expect?
This is a question that has come up before. One possibility is for the hub driver to keep track of how often it gets connect changes on each port and to ignore events when too many happen too quickly. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
