1. 08 11月, 2012 2 次提交
  2. 05 11月, 2012 2 次提交
  3. 30 10月, 2012 2 次提交
    • J
      cfg80211: allow per interface TX power setting · c8442118
      Johannes Berg 提交于
      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: NJohannes Berg <johannes.berg@intel.com>
      c8442118
    • J
      nl80211: move "can set channel" check · 71fe96bf
      Johannes Berg 提交于
      Setting the wdev to NULL when the channel can't be
      set for that interface type (to treat the channel
      setting for the wiphy/monitor) currently works, but
      is confusing in the code if netdev/wdev aren't both
      set/unset in the same way. Move the check whether
      the channel can be set to where it's needed so that
      wdev and netdev are always both assigned or NULL.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      71fe96bf
  4. 24 10月, 2012 1 次提交
  5. 18 10月, 2012 6 次提交
  6. 17 10月, 2012 2 次提交
  7. 19 9月, 2012 1 次提交
  8. 11 9月, 2012 1 次提交
  9. 05 9月, 2012 1 次提交
  10. 20 8月, 2012 1 次提交
    • J
      cfg80211: add P2P Device abstraction · 98104fde
      Johannes Berg 提交于
      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: NJohannes Berg <johannes.berg@intel.com>
      98104fde
  11. 17 7月, 2012 3 次提交
  12. 13 7月, 2012 2 次提交
  13. 12 7月, 2012 3 次提交
  14. 09 7月, 2012 4 次提交
  15. 05 7月, 2012 1 次提交
  16. 29 6月, 2012 5 次提交
  17. 28 6月, 2012 1 次提交
  18. 27 6月, 2012 1 次提交
  19. 26 6月, 2012 1 次提交