Do you think that once your latest khubd changes are applied we can get usb_reset_device() into working shape? The necessary changes won't be very large:
Yes, I do think that. Some key parts are in the gadget-2.6 tree, and I think you've listed the main remaining issues:
Those key parts are all contained within hub.c and usb.c, right?
Mostly at the end of hub.c ... except for the calls to usb_reset_device(). There's a call from usbfs.
We can even provide support for the "device morphed" case, simply by...
disabling the port. The khubd thread will see the enable-changed status
sometime later and will initiate a disconnect and another port reset.
It's a roundabout technique, since it involves destroying and then re-creating the device structure and resetting the port twice. For now it should be good enough, though.
Destroying the device structure is probably better ... and re-using that known-working infrastructure is better than "good enough". :)
Feel like finishing that up, possibly starting with what's now in the gadget-2.6 tree?
Okay, once the current outstanding changes are installed.
Great!
- Dave
------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
