1. 03 12月, 2013 1 次提交
  2. 26 11月, 2013 3 次提交
  3. 28 10月, 2013 1 次提交
    • C
      {nl,cfg,mac}80211: implement mesh channel switch userspace API · b8456a14
      Chun-Yeow Yeoh 提交于
      Implement the required procedures for mesh channel switching as defined
      in the IEEE Std 802.11-2012 section 10.9.8.4.3 and also handle the CSA
      and MCSP elements as followed:
       * Add the function for updating the beacon and probe response frames
         with CSA and MCSP elements during the period of switching to the new
         channel. Both CSA and MCSP elements must be included in beacon and
         probe response frames until the intended channel switch time.
       * The ifmsh->csa_settings is set to NULL and the CSA and MCSP elements
         will then be removed from the beacon or probe response frames once the
         new channel is switched to.
      Signed-off-by: NChun-Yeow Yeoh <yeohchunyeow@cozybit.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      b8456a14
  4. 01 10月, 2013 1 次提交
    • M
      mac80211: support reporting A-MSDU subframes individually · 0cfcefef
      Michal Kazior 提交于
      Some devices may not be able to report A-MSDUs in
      single buffers. Drivers for such devices were
      forced to re-assemble A-MSDUs which would then
      be eventually disassembled by mac80211. This could
      lead to CPU cache thrashing and poor performance.
      
      Since A-MSDU has a single sequence number all
      subframes share it. This was in conflict with
      retransmission/duplication recovery
      (IEEE802.11-2012: 9.3.2.10).
      
      Patch introduces a new flag that is meant to be
      set for all individually reported A-MSDU subframes
      except the last one. This ensures the
      last_seq_ctrl is updated after the last subframe
      is processed. If an A-MSDU is actually a duplicate
      transmission all reported subframes will be
      properly discarded.
      Signed-off-by: NMichal Kazior <michal.kazior@tieto.com>
      [johannes: add braces that were missing even before]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      0cfcefef
  5. 27 9月, 2013 1 次提交
  6. 26 9月, 2013 1 次提交
  7. 23 8月, 2013 1 次提交
  8. 16 8月, 2013 1 次提交
    • J
      mac80211: perform power save processing before decryption · 86c228a7
      Johan Almbladh 提交于
      This patch decouples the power save processing from the frame decryption
      by running the decrypt rx handler after sta_process. In the case where
      the decryption failed for some reason, the stack used to not process
      the PM and MOREDATA bits for that frame. The stack now always performs
      power save processing regardless of the decryption result. That means that
      encrypted data frames and NULLFUNC frames are now handled in the same way
      regarding power save processing, making the stack more robust.
      Signed-off-by: NJohan Almbladh <ja@anyfi.net>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      86c228a7
  9. 16 7月, 2013 4 次提交
  10. 04 6月, 2013 1 次提交
    • J
      cfg80211/mac80211: clean up cfg80211 SME APIs · 6ff57cf8
      Johannes Berg 提交于
      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: NJohannes Berg <johannes.berg@intel.com>
      6ff57cf8
  11. 24 5月, 2013 1 次提交
  12. 17 5月, 2013 3 次提交
  13. 19 4月, 2013 1 次提交
  14. 16 4月, 2013 2 次提交
  15. 11 4月, 2013 1 次提交
  16. 11 3月, 2013 1 次提交
  17. 06 3月, 2013 3 次提交
  18. 15 2月, 2013 6 次提交
  19. 12 2月, 2013 1 次提交
  20. 05 2月, 2013 1 次提交
    • M
      mac80211: mesh power save basics · 3f52b7e3
      Marco Porsch 提交于
      Add routines to
      - maintain a PS mode for each peer and a non-peer PS mode
      - indicate own PS mode in transmitted frames
      - track neighbor STAs power modes
      - buffer frames when neighbors are in PS mode
      - add TIM and Awake Window IE to beacons
      - release frames in Mesh Peer Service Periods
      
      Add local_pm to sta_info to represent the link-specific power
      mode at this station towards the remote station. When a peer
      link is established, use the default power mode stored in mesh
      config. Update the PS status if the peering status of a neighbor
      changes.
      Maintain a mesh power mode for non-peer mesh STAs. Set the
      non-peer power mode to active mode during peering. Authenticated
      mesh peering is currently not working when either node is
      configured to be in power save mode.
      
      Indicate the current power mode in transmitted frames. Use QoS
      Nulls to indicate mesh power mode transitions.
      For performance reasons, calls to the function setting the frame
      flags are placed in HWMP routing routines, as there the STA
      pointer is already available.
      
      Add peer_pm to sta_info to represent the peer's link-specific
      power mode towards the local station. Add nonpeer_pm to
      represent the peer's power mode towards all non-peer stations.
      Track power modes based on received frames.
      
      Add the ps_data structure to ieee80211_if_mesh (for TIM map, PS
      neighbor counter and group-addressed frame buffer).
      
      Set WLAN_STA_PS flag for STA in PS mode to use the unicast frame
      buffering routines in the tx path. Update num_sta_ps to buffer
      and release group-addressed frames after DTIM beacons.
      
      Announce the awake window duration in beacons if in light or
      deep sleep mode towards any peer or non-peer. Create a TIM IE
      similarly to AP mode and add it to mesh beacons. Parse received
      Awake Window IEs and check TIM IEs for buffered frames.
      
      Release frames towards peers in mesh Peer Service Periods. Use
      the corresponding trigger frames and monitor the MPSP status.
      Append a QoS Null as trigger frame if neccessary to properly end
      the MPSP. Currently, in HT channels MPSPs behave imperfectly and
      show large delay spikes and frame losses.
      Signed-off-by: NMarco Porsch <marco@cozybit.com>
      Signed-off-by: NIvan Bezyazychnyy <ivan.bezyazychnyy@gmail.com>
      Signed-off-by: NMike Krinkin <krinkin.m.u@gmail.com>
      Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      3f52b7e3
  21. 03 1月, 2013 1 次提交
  22. 06 12月, 2012 1 次提交
    • M
      mac80211: don't drop mesh peering frames from unknown STA · 815b8092
      Marco Porsch 提交于
      Previously, mesh peering frames from a STA without a station
      entry were being dropped.
      
      Mesh Peering Open and other frames (WLAN_CATEGORY_SELF_PROTECTED)
      are valid mesh peering frames even if received from a yet unknown
      station; the STA entry will be created in mesh_peer_init later.
      
      The problem didn't occur previously since both STAs receive each
      other's beacons which created the STA entry. However, this causes
      an unnecessary delay and beacons might not be received if either
      node is in PS mode.
      Signed-off-by: NMarco Porsch <marco.porsch@etit.tu-chemnitz.de>
      [reword commit log a bit]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      815b8092
  23. 05 12月, 2012 1 次提交
  24. 28 11月, 2012 1 次提交
  25. 27 11月, 2012 1 次提交