On Friday 31 October 2008, David Kilroy wrote: > The recent patch to load orinoco firmware correctly on resume simply > kept the firmware in RAM for the entire time the module was loaded, and > only applied to Agere firmware. > > The first patch uses the new power management notifiers to load and > release the firmware prior to suspend and after resume (for both Agere > and Symbol). I'm not an expert on where suspend/resume is headed, so I'd > appreciate any advice from linux-pm on whether this is the preferred way > to do things. > I tested this and it works, and looking how callbacks are invoked I think it is techically correct. But I have some concerns about general idea of requesting firmware multiple times that are not related to PM. Many properties for the currently running device/driver instance depend on particular firmware type and version. Now we blindly replace firmware; how can we be sure it is actually the same one as was at the time feature set was detected? Even if some sort of checksumming were impemented we still have to be prepared to completely reinitialize card on FW mismatch. I checked what the rest of drivers/net does and either they do not cache at all (does not work in this case) or they cache FW im memory after initial request. Comments?
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
