1. 23 Nov, 2012 2 commits
    • Johannes Berg's avatar
      mac80211: rename IEEE80211_STA_DISABLE_11N to HT · a8243b72
      Johannes Berg authored
      Since the 11n spec amendment was rolled into the
      2012 version, "11n" no longer makes sense. Use
      "HT" instead.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Johannes Berg's avatar
      mac80211: fix RX chains configuration · 76c5fa0f
      Johannes Berg authored
      If the driver doesn't support 40 MHz channels, then
      mac80211 erroneously sets number of RX chains to one
      although the number of chains is independent of the
      support for 40 MHz channels.
      Fix this by checking the 40 MHz support only for the
      code that sets the 40 MHz channel not the complete
      HT code block.
      This also means the HT20 channel type will always be
      set in the changed code block so there's no need to
      set it in case we override the AP due to invalid IEs
      in the probe response/beacon.
      The indentation is a bit quirky, but I'm rewriting
      this code for VHT support so this will change again
      very soon.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  2. 06 Nov, 2012 1 commit
  3. 05 Nov, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: send deauth only with channel context · 86552017
      Johannes Berg authored
      When userspace asks to deauthenticate and we're just
      authenticated (or still authenticating) send a deauth
      frame instead of deleting the auth request.
      On the other hand, if we've just disassociated and
      therefore deleted all our state already, drop the
      deauth request because we no longer have a channel
      context to send it on.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  4. 30 Oct, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: handle TX power per virtual interface · 1ea6f9c0
      Johannes Berg authored
      Even before channel contexts/multi-channel, having a
      single global TX power limit was already problematic,
      in particular if two managed interfaces connected to
      two APs with different power constraints. The channel
      context introduction completely broke this though and
      in fact I had disabled TX power configuration there
      for drivers using channel contexts.
      Change everything to track TX power per interface so
      that different user settings and different channel
      maxima are treated correctly. Also continue tracking
      the global TX power though for compatibility with
      applications that attempt to configure the wiphy's
      TX power globally.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  5. 25 Oct, 2012 1 commit
  6. 18 Oct, 2012 1 commit
  7. 17 Oct, 2012 8 commits
  8. 15 Oct, 2012 1 commit
  9. 21 Sep, 2012 1 commit
  10. 14 Sep, 2012 2 commits
  11. 07 Sep, 2012 1 commit
  12. 06 Sep, 2012 2 commits
  13. 04 Sep, 2012 1 commit
  14. 20 Aug, 2012 6 commits
  15. 01 Aug, 2012 2 commits
  16. 31 Jul, 2012 9 commits