On Wed, 28 Jul 2004, Marcel Holtmann wrote: > I can't tell you that right now, because the 2.4 version was different > and I haven't used the usb_set_configuration() call outside the probe() > routine. My plan is to do it this way: > > probe() > switch (configuration) > case 1: > load_firmware() > schedule_work() > set_config(2) > case 2: > register_device() > > If I use usb_set_configuration() I expect that the USB core will > disconnect the interface with the current configuration and probe > another one with the new configuration.
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. 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
