On Mon, 3 Oct 2005 04:15:49 -0400, Glenn Maynard <[EMAIL PROTECTED]> wrote: > On Tue, Sep 20, 2005 at 02:00:51PM -0700, Pete Zaitcev wrote: > > This code appears to be more trouble than it's worth, considering that > > no normal users reload drivers. So, we comment it for now. It is not > > removed outright for the benefit of hackers (that is, myself). > > My scripts reload drivers during the patch loading process: we load a > standard, stock system on boot, and then unload and reload modules from > a patch if one is installed. So, if this reset is needed for reloading > modules, it'll cause drives to fail if they're left plugged in at boot. > That isn't "normal users", but it's a practical non-development case. > Just FYI.
The clearing is needed only if a device is attached across the driver reload, and if you cannot tolerate a command failure (most likely, an open(2) would fail). If a device gets connected after the reload, it's all the same. I am sure this should not be an issue in arcade applications, where players plug keys in as save media. -- Pete ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
