1. 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>
      1ea6f9c0
  2. 25 Oct, 2012 1 commit
  3. 18 Oct, 2012 1 commit
  4. 17 Oct, 2012 8 commits
  5. 15 Oct, 2012 1 commit
  6. 21 Sep, 2012 1 commit
  7. 14 Sep, 2012 2 commits
  8. 07 Sep, 2012 1 commit
  9. 06 Sep, 2012 2 commits
  10. 04 Sep, 2012 1 commit
  11. 20 Aug, 2012 6 commits
  12. 01 Aug, 2012 2 commits
  13. 31 Jul, 2012 9 commits
  14. 17 Jul, 2012 1 commit
    • Eliad Peller's avatar
      mac80211: go out of PS before sending disassoc · 88bc40e8
      Eliad Peller authored
      
      
      on disassoc, ieee80211_set_disassoc() goes out of PS
      before indicating BSS_CHANGED_ASSOC (not sure why this
      is needed, but some drivers might count on the current
      behavior).
      
      However, it does it after sending the disassoc
      frame, which results in null-data frame being sent
      (in order to go out of ps) after we were already sent
      the disassoc, which is invalid.
      
      Fix it by going out of ps before sending the disassoc.
      Signed-off-by: default avatarEliad Peller <eliad@wizery.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      88bc40e8
  15. 12 Jul, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: add time synchronisation with BSS for assoc · 8c358bcd
      Johannes Berg authored
      
      
      Some drivers (iwlegacy, iwlwifi and rt2x00) today use the
      bss_conf.last_tsf value. By itself though that value is
      completely worthless since it may be ancient. What really
      is needed is synchronisation between some device time and
      the TSF.
      
      To clarify this, rename bss_conf.last_tsf to sync_tsf and
      add sync_device_ts which is obtained from rx_status which
      gets a new field device_timestamp for this purpose. This
      is intentionally not using the mactime field since that
      is used for other things and in IBSS is expected to sync
      with the IBSS's TSF which isn't necessarily true for the
      device timestamp.
      
      Also, since we have the information and it's useful even
      before the connection has been established, give all the
      timing details to the driver before authenticating.
      Reviewed-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8c358bcd
  16. 09 Jul, 2012 2 commits