Wolfgang Mües wrote:
echo 2 > $DEVPATH/bConfigurationValue
The hotplug script is executed _before_ probe() is called? Even if the driver is already in memory? And the sysfs is doing the set_configuration() before probe() is called?
There's a "device" hotplug call, where $DEVPATH/bConfigurationValue exists ... it'll be zero when the hotplug event fires, but (for now) very likely not when that event is triggered.
Later there's an "interface" hotplug call, where there's no such file (but there'll be bInterfaceClass etc). But there's no guarantee that this user mode logic doesn't execute before the "device" hotplug...
User mode code can use the event sequence number to order events, but that implies funneling the events through some single access channel. Which folk want to do lately, for various reasons.
- Dave
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
