iwlagn: track beacon interval sent to device

Browse source

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>

...

This commit is contained in:

Johannes Berg 2011-07-18 01:59:22 -07:00 • committed by Wey-Yi Guy

parent 21489ec2f1

commit bbb05cb55a

3 changed files with 9 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

11

drivers/net/wireless/iwlwifi/iwl-agn-rxon.c

View file

2

drivers/net/wireless/iwlwifi/iwl-core.c

View file

2

drivers/net/wireless/iwlwifi/iwl-dev.h

View file