1. 24 2月, 2016 1 次提交
    • L
      cfg80211: basic support for PBSS network type · 34d50519
      Lior David 提交于
      PBSS (Personal Basic Service Set) is a new BSS type for DMG
      networks. It is similar to infrastructure BSS, having an AP-like
      entity called PCP (PBSS Control Point), but it has few differences.
      PBSS support is mandatory for 11ad devices.
      
      Add support for PBSS by introducing a new PBSS flag attribute.
      The PBSS flag is used in the START_AP command to request starting
      a PCP instead of an AP, and in the CONNECT command to request
      connecting to a PCP instead of an AP.
      Signed-off-by: NLior David <liord@codeaurora.org>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      34d50519
  2. 02 2月, 2016 1 次提交
  3. 26 1月, 2016 2 次提交
    • L
      wil6210: use extra IEs from probe response · c100c883
      Lior David 提交于
      In the start_ap/change_beacon API, when we set up probe response
      offloading, we only use the IE list from the probe response
      template and not the IE list from the proberesp_ies argument.
      As a result, we miss important IEs and it causes problems with
      some scenarios such as P2P.
      With this change, we merge the list of IEs from the probe response
      template and proberesp_ies and send the merged list to the FW
      for offloading. It is still FW responsibility to filter out
      irrelevant IEs when sending probe response, based on the actual
      contents of the probe request.
      Also in case association response termplate is not provided,
      we will use the merged list of IEs from probe response in the
      association response as well.
      Signed-off-by: NLior David <qca_liord@qca.qualcomm.com>
      Signed-off-by: NMaya Erez <qca_merez@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      c100c883
    • L
      wil6210: fix privacy flag calculation in change_beacon · c5a157e4
      Lior David 提交于
      Currently the privacy flag calculation in change_beacon
      checks for RSN IE inside proberesp_ies, but normally it
      is not found there. It works today because of code inside
      the function wil_fix_bcon, but wil_fix_bcon is not directly
      related to change_beacon, and it may be changed or removed
      in the future and break the calculation.
      To fix this issue, change the privacy flag calculation
      to check RSN IE inside the beacon itself. The new check is more
      reliable and will not be sensitive to changes in wil_fix_bcon.
      Signed-off-by: NLior David <qca_liord@qca.qualcomm.com>
      Signed-off-by: NMaya Erez <qca_merez@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      c5a157e4
  4. 06 8月, 2015 2 次提交
  5. 30 6月, 2015 1 次提交
  6. 09 6月, 2015 1 次提交
  7. 05 5月, 2015 3 次提交
  8. 29 4月, 2015 3 次提交
  9. 20 3月, 2015 2 次提交
  10. 13 3月, 2015 1 次提交
  11. 03 3月, 2015 1 次提交
    • D
      cfg80211: add bss_type and privacy arguments in cfg80211_get_bss() · 6eb18137
      Dedy Lansky 提交于
      802.11ad adds new a network type (PBSS) and changes the capability
      field interpretation for the DMG (60G) band.
      The same 2 bits that were interpreted as "ESS" and "IBSS" before are
      re-used as a 2-bit field with 3 valid values (and 1 reserved). Valid
      values are: "IBSS", "PBSS" (new) and "AP".
      
      In order to get the BSS struct for the new PBSS networks, change the
      cfg80211_get_bss() function to take a new enum ieee80211_bss_type
      argument with the valid network types, as "capa_mask" and "capa_val"
      no longer work correctly (the search must be band-aware now.)
      
      The remaining bits in "capa_mask" and "capa_val" are used only for
      privacy matching so replace those two with a privacy enum as well.
      Signed-off-by: NDedy Lansky <dlansky@codeaurora.org>
      [rewrite commit log, tiny fixes]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      6eb18137
  12. 27 2月, 2015 2 次提交
  13. 03 2月, 2015 1 次提交
  14. 29 1月, 2015 4 次提交
  15. 15 1月, 2015 1 次提交
  16. 08 1月, 2015 1 次提交
    • J
      cfg80211: remove enum station_info_flags · 319090bf
      Johannes Berg 提交于
      This is really just duplicating the list of information that's
      already available in the nl80211 attribute, so remove the list.
      Two small changes are needed:
       * remove STATION_INFO_ASSOC_REQ_IES complete, but the length
         (assoc_req_ies_len) can be used instead
       * add NL80211_STA_INFO_RX_DROP_MISC which exists internally
         but not in nl80211 yet
      
      This gets rid of the duplicate maintenance of the two lists.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      319090bf
  17. 02 12月, 2014 1 次提交
  18. 31 10月, 2014 1 次提交
    • V
      wil6210: prevent double disconnect command issuing · b516fcc5
      Vladimir Kondratiev 提交于
      Disconnect flow may be invoked either from upper layer request,
      or from event reported by the firmware.
      
      In case of firmware event, driver need to release resources for the station but
      not send another disconnect WMI command.
      
      In case of upper layer request, WMI_DISCONNECT_STA_CMDID command need to
      be issued for the firmware to perform disconnect on the MAC layer. Eventually,
      event is expected to confirm MAC disconnect, but it is better to not wait for
      firmware event and release station resources immediately. FW may fail to
      report disconnect for various reasons, so one could not rely on event always reported.
      
      Introduce parameter to distinguish 2 cases above to prevent double WMI command
      issuing.
      Signed-off-by: NVladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b516fcc5
  19. 20 10月, 2014 1 次提交
  20. 03 10月, 2014 1 次提交
    • V
      wil6210: manual FW error recovery mode · c33407a8
      Vladimir Kondratiev 提交于
      Introduce manual FW recovery mode. It is activated if module parameter
      @no_fw_recovery set to true. May be changed at runtime.
      
      Recovery information provided by new "recovery" debugfs file. It prints:
      
      mode = [auto|manual]
      state = [idle|pending|running]
      
      In manual mode, after FW error, recovery won't start automatically. Instead,
      after notification to user space, recovery waits in "pending" state, as indicated by the
      "recovery" debugfs file. User space tools may perform data collection and allow to
      continue recovery by writing "run" to the "recovery" debugfs file.
      Alternatively, recovery pending may be canceled by stopping network interface
      i.e. 'ifconfig wlan0 down'
      Signed-off-by: NVladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      c33407a8
  21. 12 9月, 2014 7 次提交
  22. 26 8月, 2014 2 次提交