1. 08 2月, 2013 2 次提交
  2. 02 2月, 2013 2 次提交
  3. 31 1月, 2013 2 次提交
  4. 26 1月, 2013 2 次提交
  5. 24 1月, 2013 2 次提交
  6. 23 1月, 2013 4 次提交
  7. 19 1月, 2013 2 次提交
  8. 18 1月, 2013 2 次提交
  9. 17 1月, 2013 5 次提交
    • S
      cfg80211: check radar interface combinations · 11c4a075
      Simon Wunderlich 提交于
      To ease further DFS development regarding interface combinations, use
      the interface combinations structure to test for radar capabilities.
      Drivers can specify which channel widths they support, and in which
      modes. Right now only a single AP interface is allowed, but as the
      DFS code evolves other combinations can be enabled.
      Signed-off-by: NSimon Wunderlich <siwu@hrz.tu-chemnitz.de>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      11c4a075
    • J
      cfg80211: Allow use_mfp to be specified with the connect command · cee00a95
      Jouni Malinen 提交于
      The NL80211_ATTR_USE_MFP attribute was originally added for
      NL80211_CMD_ASSOCIATE, but it is actually as useful (if not even more
      useful) with NL80211_CMD_CONNECT, so process that attribute with the
      connect command, too.
      Signed-off-by: NJouni Malinen <jouni@qca.qualcomm.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      cee00a95
    • A
      nl80211: allow user-space to set address for P2P_DEVICE · 1c18f145
      Arend van Spriel 提交于
      As per email discussion Jouni Malinen pointed out that:
      
      "P2P message exchanges can be executed on the current operating channel
      of any operation (both P2P and non-P2P station). These can be on 5 GHz
      and even on 60 GHz (so yes, you _can_ do GO Negotiation on 60 GHz).
      
      As an example, it would be possible to receive a GO Negotiation Request
      frame on a 5 GHz only radio and then to complete GO Negotiation on that
      band. This can happen both when connected to a P2P group (through client
      discoverability mechanism) and when connected to a legacy AP (assuming
      the station receive Probe Request frame from full scan in the beginning
      of P2P device discovery)."
      
      This means that P2P messages can be sent over different radio devices.
      However, these should use the same P2P device address so it should be
      able to provision this from user-space. This patch adds a parameter for
      this to struct vif_params which should only be used during creation of
      the P2P device interface.
      
      Cc: Jouni Malinen <j@w1.fi>
      Cc: Greg Goldman <ggoldman@broadcom.com>
      Cc: Jithu Jance <jithu@broadcom.com>
      Signed-off-by: NArend van Spriel <arend@broadcom.com>
      [add error checking]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      1c18f145
    • M
      {cfg,nl}80211: mesh power mode primitives and userspace access · 3b1c5a53
      Marco Porsch 提交于
      Add the nl80211_mesh_power_mode enumeration which holds possible
      values for the mesh power mode. These modes are unknown, active,
      light sleep and deep sleep.
      
      Add power_mode entry to the mesh config structure to hold the
      user-configured default mesh power mode. This value will be used
      for new peer links.
      
      Add the dot11MeshAwakeWindowDuration value to the mesh config.
      The awake window is a duration in TU describing how long the STA
      will stay awake after transmitting its beacon in PS mode.
      
      Add access routines to:
       - get/set local link-specific power mode (STA)
       - get remote STA's link-specific power mode (STA)
       - get remote STA's non-peer power mode (STA)
       - get/set default mesh power mode (mesh config)
       - get/set mesh awake window duration (mesh config)
      
      All config changes may be done at mesh runtime and take effect
      immediately.
      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>
      [fix commit message line length, error handling in set station]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      3b1c5a53
    • M
      {cfg,nl,mac}80211: set beacon interval and DTIM period on mesh join · 9bdbf04d
      Marco Porsch 提交于
      Move the default mesh beacon interval and DTIM period to cfg80211
      and make them accessible to nl80211. This enables setting both
      values when joining an MBSS.
      
      Previously the DTIM parameter was not set by mac80211 so the
      driver's default value was used.
      Signed-off-by: NMarco Porsch <marco@cozybit.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      9bdbf04d
  10. 16 1月, 2013 2 次提交
  11. 15 1月, 2013 1 次提交
  12. 14 1月, 2013 2 次提交
  13. 12 1月, 2013 2 次提交
  14. 10 1月, 2013 7 次提交
  15. 08 1月, 2013 1 次提交
  16. 03 1月, 2013 2 次提交