Of course, there's another problem that's equally bad but less solvable. If the SET_CONFIGURATION message fails, the device is left in an unknown state, probably the same state as it was in before. But we have already disabled all the interfaces and unbound all the drivers.
Actually it's in USB_STATE_ADDRESS from the host's perspective, although the device may think otherwise. The host certainly isn't going to talk to anything except ep0 until some SET_CONFIG request succeeds, which will correct any substantial disagreements between the two. I don't see what the problem would be..
- Dave
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
