1. 26 Nov, 2012 1 commit
    • Johannes Berg's avatar
      cfg80211: remove remain-on-channel channel type · 42d97a59
      Johannes Berg authored
      
      
      As mwifiex (and mac80211 in the software case) are the
      only drivers actually implementing remain-on-channel
      with channel type, userspace can't be relying on it.
      This is the case, as it's used only for P2P operations
      right now.
      
      Rather than adding a flag to tell userspace whether or
      not it can actually rely on it, simplify all the code
      by removing the ability to use different channel types.
      Leave only the validation of the attribute, so that if
      we extend it again later (with the needed capability
      flag), it can't break userspace sending invalid data.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      42d97a59
  2. 19 Nov, 2012 1 commit
    • Jouni Malinen's avatar
      cfg80211: Add TDLS event to allow drivers to request operations · 3475b094
      Jouni Malinen authored
      
      
      The NL80211_CMD_TDLS_OPER command was previously used only for userspace
      request for the kernel code to perform TDLS operations. However, there
      are also cases where the driver may need to request operations from
      userspace, e.g., when using security on the AP path. Add a new cfg80211
      function for generating a TDLS operation event for drivers to request a
      new link to be set up (NL80211_TDLS_SETUP) or an existing link to be
      torn down (NL80211_TDLS_TEARDOWN). Drivers can optionally use these
      events, e.g., based on noticing data traffic being sent to a peer
      station that is seen with good signal strength.
      Signed-off-by: default avatarJouni Malinen <jouni@qca.qualcomm.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      3475b094
  3. 12 Nov, 2012 1 commit
  4. 05 Nov, 2012 1 commit
  5. 30 Oct, 2012 1 commit
    • Johannes Berg's avatar
      cfg80211: allow per interface TX power setting · c8442118
      Johannes Berg authored
      
      
      The TX power setting is currently per wiphy (hardware
      device) but with multi-channel capabilities that doesn't
      make much sense any more.
      
      Allow drivers (and mac80211) to advertise support for
      per-interface TX power configuration. When the TX power
      is configured for the wiphy, the wdev will be NULL and
      the driver can still handle that, but when a wdev is
      given the TX power can be set only for that wdev now.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      c8442118
  6. 18 Oct, 2012 4 commits
  7. 17 Oct, 2012 2 commits
  8. 13 Oct, 2012 1 commit
  9. 18 Sep, 2012 1 commit
  10. 20 Aug, 2012 1 commit
    • Johannes Berg's avatar
      cfg80211: add P2P Device abstraction · 98104fde
      Johannes Berg authored
      
      
      In order to support using a different MAC address
      for the P2P Device address we must first have a
      P2P Device abstraction that can be assigned a MAC
      address.
      
      This abstraction will also be useful to support
      offloading P2P operations to the device, e.g.
      periodic listen for discoverability.
      
      Currently, the driver is responsible for assigning
      a MAC address to the P2P Device, but this could be
      changed by allowing a MAC address to be given to
      the NEW_INTERFACE command.
      
      As it has no associated netdev, a P2P Device can
      only be identified by its wdev identifier but the
      previous patches allowed using the wdev identifier
      in various APIs, e.g. remain-on-channel.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      98104fde
  11. 17 Jul, 2012 2 commits
  12. 09 Jul, 2012 1 commit
    • Johannes Berg's avatar
      nl80211: prepare for non-netdev wireless devs · 89a54e48
      Johannes Berg authored
      
      
      In order to support a P2P device abstraction and
      Bluetooth high-speed AMPs, we need to have a way
      to identify virtual interfaces that don't have a
      netdev associated.
      
      Do this by adding a NL80211_ATTR_WDEV attribute
      to identify a wdev which may or may not also be
      a netdev.
      
      To simplify things, use a 64-bit value with the
      high 32 bits being the wiphy index for this new
      wdev identifier in the nl80211 API.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      89a54e48
  13. 05 Jul, 2012 1 commit
  14. 02 Jul, 2012 1 commit
  15. 28 Jun, 2012 1 commit
  16. 26 Jun, 2012 1 commit
  17. 18 Jun, 2012 1 commit
  18. 14 Jun, 2012 1 commit
  19. 13 Jun, 2012 2 commits
  20. 11 Jun, 2012 1 commit
  21. 06 Jun, 2012 1 commit
  22. 05 Jun, 2012 2 commits
  23. 16 May, 2012 1 commit
  24. 15 May, 2012 1 commit
  25. 08 May, 2012 1 commit
  26. 11 Apr, 2012 1 commit
  27. 10 Apr, 2012 2 commits
  28. 12 Mar, 2012 1 commit
  29. 06 Mar, 2012 1 commit
  30. 05 Mar, 2012 2 commits
  31. 22 Feb, 2012 1 commit