David:
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:
Rename usb_physical_reset_device to usb_reset_device (and
get rid of the subroutine that currently has that name).
Change the API to require that the caller holds the
usbdev->serialize lock.
Go through the various callers to make sure they really do
hold the lock (usb-storage will need some changes but I can
take care of them easily).
Make the routine read the configuration descriptors and verify
them against the raw descriptor values already in memory.
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.
While it's debatable whether this is the _best_ way to handle it, it ought
to work.
Alan Stern
-------------------------------------------------------
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
