On Fri, 16 Jan 2004, Stavros Markou wrote: > Alan Stern wrote: > > >I took a quick look at your file. Making reset_device() call > >destroy_configuration() and get_configuration() like you do is very > >unsafe. No wonder you're getting kernel panics! > > > > > > > destroy_configuration and get_configuration are taken from the current > stable kernel.
Yes, and they are a large part of the reason the standard kernel doesn't work when you do a firmware update & reset during probe(). > >Here's an alternate approach you could try. Create a userspace driver > >that uses libfs or usbfs to take care of the DFU and device reset. Once > >that's done, load your kernel driver and let it carry on. > > > > > > > I want the procedure to be transparent for the simple user. How can I > achieve that with two drivers (user-space, kernel-space)? > In the future if anything happens to a usb device like a failure to a > command over the control endpoint then the driver will be able to reset > the device ? You may be able to use hotplug scripts to do what you need. Reset is okay so long as the descriptors don't change. Even if they do, reset is probably okay so long as it's not during probe() -- but I'm not sure of that. Alan Stern ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
