> > The effort of keeping track of all the N-second timeouts and devices being
> > probed sounds a little messy. But no doubt it can be done.
>
> Simple to do: one bit in the config, "did we probe this yet";
> and the device records the last-probe-ed time. The rest just
> needs a timer ... and something to do the deferred work bit,
> which we do agree needs to exist.
No need to use timers. There's a small, limited number of events that
should cause reprobing
- no driver registered
- device reset (usbfs)
- interface being unclaimed (for drivers that want several interfaces)
- changes in the power bugdet
- firmware download
But we'd have to record user space explicitely choosing one configuration.
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
