1. 28 Nov, 2014 1 commit
  2. 27 Nov, 2014 1 commit
  3. 26 Nov, 2014 2 commits
  4. 25 Nov, 2014 1 commit
  5. 19 Nov, 2014 7 commits
  6. 10 Nov, 2014 2 commits
  7. 04 Nov, 2014 2 commits
  8. 31 Oct, 2014 1 commit
  9. 29 Oct, 2014 1 commit
  10. 27 Oct, 2014 1 commit
  11. 22 Oct, 2014 1 commit
    • Johannes Berg's avatar
      cfg80211: make WMM TSPEC support flag an nl80211 feature flag · 723e73ac
      Johannes Berg authored
      During the review of the corresponding wpa_supplicant patches we
      noticed that the only way for it to detect that this functionality
      is supported currently is to check for the command support. This
      can be misleading though, as the command was also designed to, in
      the future, support pure 802.11 TSPECs.
      
      Expose the WMM-TSPEC feature flag to nl80211 so later we can also
      expose an 802.11-TSPEC feature flag (if needed) to differentiate
      the two cases.
      
      Note: this change isn't needed in 3.18 as there's no driver there
      yet that supports the functionality at all.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      723e73ac
  12. 20 Oct, 2014 2 commits
  13. 09 Oct, 2014 2 commits
  14. 11 Sep, 2014 6 commits
  15. 05 Sep, 2014 3 commits
  16. 03 Sep, 2014 1 commit
  17. 26 Aug, 2014 1 commit
    • Johannes Berg's avatar
      cfg80211: clarify BSS probe response vs. beacon data · 0e227084
      Johannes Berg authored
      There are a few possible cases of where BSS data came from:
       1) only a beacon has been received
       2) only a probe response has been received
       3) the driver didn't report what it received (this happens when
          using cfg80211_inform_bss[_width]())
       4) both probe response and beacon data has been received
      
      Unfortunately, in the userspace API, a few things weren't there:
       a) there was no way to differentiate cases 1) and 4) above
          without comparing the data of the IEs
       b) the TSF was always from the last frame, instead of being
          exposed for beacon/probe response separately like IEs
      
      Fix this by
         i) exporting a new flag attribute that indicates whether or
            not probe response data has been received - this addresses (a)
        ii) exporting a BEACON_TSF attribute that holds the beacon's TSF
            if a beacon has been received
       iii) not exporting the beacon attributes in case (3) above as that
            would just lead userspace into thinking the data actually came
            from a beacon when that isn't clear
      
      To implement this, track inside the IEs struct whether or not it
      (definitely) came from a beacon.
      
      Reported-by: William Seto
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      0e227084
  18. 21 Jul, 2014 1 commit
  19. 25 Jun, 2014 1 commit
  20. 24 Jun, 2014 1 commit
  21. 23 Jun, 2014 1 commit
  22. 26 May, 2014 1 commit