> My feeling is that the kernel should _not_ save the firmware during a D3
> suspend. When the resume takes place the device should be unregistered
> and subsequently reprobed. Then the firmware can be loaded again by the
> same mechanism that loaded it in the first place.
Upon second thought, user space should write the firmware _before_
it initiates suspend, so that the firmware is part of the image as it is
read back. If you request a suspend without writing firmware, it's
your fault. You brake it, you can keep the pieces.
Firmware for swap devices must be in kernel always.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
