diff options
author | Johannes Berg <johannes.berg@intel.com> | 2013-05-16 00:55:45 +0200 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2013-06-04 13:03:11 +0200 |
commit | ceca7b7121795ef81bd598a240d53a925662d0c1 (patch) | |
tree | 510d7a6c578d7ede025c8b4714b9584729517b0a /net/wireless/mesh.c | |
parent | 6ff57cf88807dd81300b5b9c623dc5eb6422b9f6 (diff) | |
download | blackbird-op-linux-ceca7b7121795ef81bd598a240d53a925662d0c1.tar.gz blackbird-op-linux-ceca7b7121795ef81bd598a240d53a925662d0c1.zip |
cfg80211: separate internal SME implementation
The current internal SME implementation in cfg80211 is
very mixed up with the MLME handling, which has been
causing issues for a long time. There are three things
that the implementation has to provide:
* a basic SME implementation for nl80211's connect()
call (for drivers implementing auth/assoc, which is
really just mac80211) and wireless extensions
* MLME events for the userspace SME
* SME events (connected, disconnected etc.) for all
different SME implementation possibilities (driver,
cfg80211 and userspace)
To achieve these goals it isn't necessary to track the
software SME's connection status outside of it's state
(which is the part that caused many issues.) Instead,
track it only in the SME data (wdev->conn) and in the
general case only track whether the wdev is connected
or not (via wdev->current_bss.)
Also separate the internal implementation to not have
callbacks from the SME events, but rather call it from
the API functions that the driver (or rather mac80211)
calls. This separates the code better.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/wireless/mesh.c')
0 files changed, 0 insertions, 0 deletions