> I agree that it would ease things to provide entry points for set_config > and reset_device that require the caller to hold dev->serialize already. > The issue you and Oliver noted about holding the bus semaphore will go > away when I finally get around to rewriting usb_reset_device().
From what Dave says, usb_reset_device shouldn't take dev->serialize (but accidentally does via usb_set_configuration). That seems strange to me: I thought the point of usbfs taking dev->serialize is to protect against the device settings changing, but now we have usb_reset_device that doesn't take dev->serialize at all - and surely it changes the device settings! With much confusion, Duncan. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
