On Wed, 19 Dec 2001, Ken Hahn wrote:
> *breathing deeply*
>
> Ok, I'm just a bit frustrated. Still appreciate all that goes on here. Thank all of
>you.
> Wish all good holiday type feelings.
Ok, so you have a device that needs a firmware download to be supported by
the ordinary usb storage driver ?
Furthermore the device is effectively bus powered ? (It'll loose power if
the bus looses power leading to a need for another load of firmware)
You can use a script the hotplug mechanism starts to download the
firmware. If the computer your adapter is attached to goes to a power
saving state that'll make your device loose its firmware, you might suffer
data corruption and killed tasks.
Just IMHO and under the conditions stated above.
Short of writing a dedicated and quite complicated driver that hooks into
the 2.4 power management subsystem there's nothing you can do about that.
If the power management demon you use allows you to run a command before
suspension, you should run sync to reduce the risk.
And for the benefit of the rest of us, here's the explanation why.
Whenever the device looses firmware it needs to reconnect. Therefore
there's a window where the device is gone in terms of usb storage.
If the vm decides to write out dirty pages to the device during that time
these attempts will fail with the usual consequences.
With the infrastructure available in 2.4 the solution to this problem must
be in kernel space and involves modifications of the usb core to hook into
power management.
Regards
Oliver
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
