1. 16 Jul, 2013 4 commits
  2. 19 Jun, 2013 1 commit
  3. 18 Jun, 2013 2 commits
  4. 11 Jun, 2013 2 commits
  5. 05 Jun, 2013 1 commit
  6. 04 Jun, 2013 2 commits
    • Johannes Berg's avatar
      cfg80211: separate internal SME implementation · ceca7b71
      Johannes Berg authored
      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: default avatarJohannes Berg <johannes.berg@intel.com>
      ceca7b71
    • Johannes Berg's avatar
      cfg80211/mac80211: clean up cfg80211 SME APIs · 6ff57cf8
      Johannes Berg authored
      Do some cleanups in the cfg80211 SME APIs, which are
      only used by mac80211.
      
      Most of these functions get a frame passed, and there
      isn't really any reason to export multiple functions
      as cfg80211 can check the frame type instead, do that.
      
      Additionally, the API functions have confusing names
      like cfg80211_send_...() which was meant to indicate
      that it sends an event to userspace, but gets a bit
      confusing when there's both TX and RX and they're not
      all clearly labeled.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      6ff57cf8
  7. 03 Jun, 2013 1 commit
  8. 29 May, 2013 2 commits
  9. 27 May, 2013 1 commit
  10. 24 May, 2013 3 commits
  11. 16 May, 2013 3 commits
  12. 22 Apr, 2013 1 commit
  13. 16 Apr, 2013 1 commit
  14. 25 Mar, 2013 1 commit
  15. 06 Mar, 2013 7 commits
  16. 15 Feb, 2013 4 commits
  17. 13 Feb, 2013 2 commits
  18. 11 Feb, 2013 2 commits
    • Johannes Berg's avatar
      cfg80211: move TSF into IEs · 8cef2c9d
      Johannes Berg authored
      While technically the TSF isn't an IE, it can be
      necessary to distinguish between the TSF from a
      beacon and a probe response, in particular in
      order to know the next DTIM TBTT, as not all APs
      are spec compliant wrt. TSF==0 being a DTIM TBTT
      and thus the DTIM count needs to be taken into
      account as well.
      
      To allow this, move the TSF into the IE struct
      so it can be known whence it came.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8cef2c9d
    • Johannes Berg's avatar
      cfg80211: remove scan ies NULL check · 83c7aa1a
      Johannes Berg authored
      There's no way scan BSS IEs can be NULL as even
      if the allocation fails the frame is discarded.
      Remove some code checking for this and document
      that it is always non-NULL.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      83c7aa1a