On 4/4/08, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > > for iwl the driver on suspend behave like the device is going down, on > > resume the driver reload the firmware and start fresh. the driver does > > save some data to restore on resume. > > Right, I think most drivers/hw behave that way. > > > I guess we can enhance on this to handle more scenario, but atleast > > this is good enough for iwl driver. > > What happens, for example, when you enable hardware crypto and set a WEP > key? With b43, after suspend/resume, mac80211 and the driver think the > key is set in hardware, but it was obviously cleared. It would of course > be possible to handle that in the driver, but I'd prefer it to be done > in mac80211 because then the driver doesn't need all the extra code. > > johannes > > That exactly what I think should happen and that why iwl need to notify the mac80211 to re-associate again, we can have the driver do that but it is cleaner and ii is more safe to have mac80211 to drive thing than have the driver try extra hard to restore to pre-suspend. I never involved in the security part of the driver so I need to look it up. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
