Disconnect is called when I unplug the wlan card. In the case of a dataflash device when device_del is called dev->parent is not NULL
but in the case of eeprom device dev->parent is NULL. My opinion is that
Hmm, it might be interesting to compare dump_stack() output at those two call sites.
Also: could you briefly summarize how those two different device types handle their firmware update? For example, one type of Atmel WLAN card uses a DFU stage, followed by some additional commands with a usb_reset_device() in there.
Before long, everything up to the reset should work from probe() routine. But 2.6.0 won't.
the use of (ex usb_physical_reset_device) by the one type of device and not the other has nothing to do with the fact that when I unplug those devices I get two distinct results.
Stavros, what patches are you running with? __usb_reset_device name suggests there are some.
I posted a disconnect patch a while back, which included that re-name, and later submitted a tweaked/fixed version in four different segments. If you're using either of those, I hope it's the latter!
- Dave
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
