...Stavros, what patches are you running with? __usb_reset_device name suggests there are some.Can you send me this patch ?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!
Either "bk clone bk://usb-gadget.bkbits.net/gadget-2.6" or apply the patches from these messages:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107281400904072&w=2 http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107325845324500&w=2 http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107329882620130&w=2 http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107369460101804&w=2
I believe that when these get merged, Alan was planning to modify the "device morphed" path so it works better with devices that use DFU-ish updates. I think you'll observe that (with usb debug enabled) these patches will identify resets that morphed the device, like your "EEPROM device" type. (Though it can't yet re-enumerate them.)
- Dave
------------------------------------------------------- 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
