iwlagn: track beacon interval sent to device
commitbbb05cb55a1b57003b17d47b5a7ac809bab60f80
authorJohannes Berg <johannes.berg@intel.com>
Mon, 18 Jul 2011 08:59:22 +0000 (18 01:59 -0700)
committerWey-Yi Guy <wey-yi.w.guy@intel.com>
Thu, 21 Jul 2011 14:31:54 +0000 (21 07:31 -0700)
tree5c3b6f5ec3f763cf5bc66fde0568ed40c6fc0750
parent21489ec2f18b56eaebc70c0dae928c1adae4c5f5
iwlagn: track beacon interval sent to device

Sometimes, when mac80211 changes the beacon
interval or when it isn't yet set in mac80211
before association, the uCode will sysassert
because we send it confusing RXON timing vs.
PAN parameters. To fix this, track the last
beacon interval sent to the device and use
that in PAN parameter calculations.

This fixes a bug during P2P group formation
as a client (and possibly association to a
regular AP) while connected to another AP.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
drivers/net/wireless/iwlwifi/iwl-agn-rxon.c
drivers/net/wireless/iwlwifi/iwl-core.c
drivers/net/wireless/iwlwifi/iwl-dev.h