1. 08 Feb, 2013 2 commits
  2. 03 Feb, 2013 2 commits
  3. 29 Jan, 2013 2 commits
  4. 28 Jan, 2013 1 commit
  5. 22 Jan, 2013 26 commits
  6. 16 Jan, 2013 7 commits
    • Johannes Berg's avatar
      mac80211: split out chandef tracing macros · 5a32aff3
      Johannes Berg authored
      Some new APIs will require tracing a chandef without
      it being part of a channel context, so separate out
      the tracing macros for that.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      5a32aff3
    • Simon Wunderlich's avatar
      cfg80211: check radar interface combinations · 11c4a075
      Simon Wunderlich authored
      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: default avatarSimon Wunderlich <siwu@hrz.tu-chemnitz.de>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      11c4a075
    • Jouni Malinen's avatar
      cfg80211: Allow use_mfp to be specified with the connect command · cee00a95
      Jouni Malinen authored
      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: default avatarJouni Malinen <jouni@qca.qualcomm.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      cee00a95
    • Bob Copeland's avatar
      mac80211: add encrypt headroom to PERR frames · 8680451f
      Bob Copeland authored
      Mesh PERR action frames are robust and thus may be encrypted, so add
      proper head/tailroom to allow this.  Fixes this warning when operating
      a Mesh STA on ath5k:
      
      WARNING: at net/mac80211/wpa.c:427 ccmp_encrypt_skb.isra.5+0x7b/0x1a0 [mac80211]()
      Call Trace:
       [<c011c5e7>] warn_slowpath_common+0x63/0x78
       [<c011c60b>] warn_slowpath_null+0xf/0x13
       [<e090621d>] ccmp_encrypt_skb.isra.5+0x7b/0x1a0 [mac80211]
       [<e090685c>] ieee80211_crypto_ccmp_encrypt+0x1f/0x37 [mac80211]
       [<e0917113>] invoke_tx_handlers+0xcad/0x10bd [mac80211]
       [<e0917665>] ieee80211_tx+0x87/0xb3 [mac80211]
       [<e0918932>] ieee80211_tx_pending+0xcc/0x170 [mac80211]
       [<c0121c43>] tasklet_action+0x3e/0x65
      Signed-off-by: default avatarBob Copeland <me@bobcopeland.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8680451f
    • Bob Copeland's avatar
      mac80211: set NEED_TXPROCESSING for PERR frames · 9cbbffe2
      Bob Copeland authored
      A user reported warnings in ath5k due to transmitting frames with no
      rates set up.  The frames were Mesh PERR frames, and some debugging
      showed an empty control block with just the vif pointer:
      
      >  [  562.522682] XXX txinfo: 00000000: 00 00 00 00 00 00 00 00 00 00 00
      >  00 00 00 00 00  ................
      >  [  562.522688] XXX txinfo: 00000010: 00 00 00 00 00 00 00 00 54 b8 f2
      >  db 00 00 00 00  ........T.......
      >  [  562.522693] XXX txinfo: 00000020: 00 00 00 00 00 00 00 00 00 00 00
      >  00 00 00 00 00  ................
      
      Set the IEEE80211_TX_INTFL_NEED_TXPROCESSING flag to ensure that
      rate control gets run before the frame is sent.
      Signed-off-by: default avatarBob Copeland <me@bobcopeland.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      9cbbffe2
    • Arend van Spriel's avatar
      nl80211: allow user-space to set address for P2P_DEVICE · 1c18f145
      Arend van Spriel authored
      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: default avatarArend van Spriel <arend@broadcom.com>
      [add error checking]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1c18f145
    • Marco Porsch's avatar
      {cfg,nl}80211: mesh power mode primitives and userspace access · 3b1c5a53
      Marco Porsch authored
      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: default avatarMarco Porsch <marco@cozybit.com>
      Signed-off-by: default avatarIvan Bezyazychnyy <ivan.bezyazychnyy@gmail.com>
      Signed-off-by: default avatarMike Krinkin <krinkin.m.u@gmail.com>
      [fix commit message line length, error handling in set station]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      3b1c5a53