1. 15 May, 2014 2 commits
  2. 13 May, 2014 1 commit
  3. 28 Apr, 2014 1 commit
  4. 25 Apr, 2014 1 commit
    • Rostislav Lisovy's avatar
      cfg80211: Add attributes describing prohibited channel bandwidth · ea077c1c
      Rostislav Lisovy authored
      Since there are frequency bands (e.g. 5.9GHz) allowing channels
      with only 10 or 5 MHz bandwidth, this patch adds attributes that
      allow keeping track about this information.
      When channel attributes are reported to user-space, make sure to
      not break old tools, i.e. if the 'split wiphy dump' is enabled,
      report the extra attributes (if present) describing the bandwidth
      restrictions.  If the 'split wiphy dump' is not enabled,
      completely omit those channels that have flags set to either
      IEEE80211_CHAN_NO_10MHZ or IEEE80211_CHAN_NO_20MHZ.
      Add the check for new bandwidth restriction flags in
      cfg80211_chandef_usable() to comply with the restrictions.
      Signed-off-by: default avatarRostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  5. 09 Apr, 2014 3 commits
  6. 25 Feb, 2014 1 commit
  7. 21 Feb, 2014 1 commit
  8. 20 Feb, 2014 2 commits
  9. 12 Feb, 2014 1 commit
  10. 05 Feb, 2014 1 commit
    • Janusz Dziedzic's avatar
      cfg80211: regulatory introduce maximum bandwidth calculation · 97524820
      Janusz Dziedzic authored
      In case we will get regulatory request with rule
      where max_bandwidth_khz is set to 0 handle this
      case as a special one.
      If max_bandwidth_khz == 0 we should calculate maximum
      available bandwidth base on all frequency contiguous rules.
      In case we need auto calculation we just have to set:
      country PL: DFS-ETSI
              (2402 - 2482 @ 40), (N/A, 20)
              (5170 - 5250 @ AUTO), (N/A, 20)
              (5250 - 5330 @ AUTO), (N/A, 20), DFS
              (5490 - 5710 @ 80), (N/A, 27), DFS
      This mean we will calculate maximum bw for rules where
      AUTO (N/A) were set, 160MHz (5330 - 5170) in example above.
      So we will get:
              (5170 - 5250 @ 160), (N/A, 20)
              (5250 - 5330 @ 160), (N/A, 20), DFS
      In other case:
      country FR: DFS-ETSI
              (2402 - 2482 @ 40), (N/A, 20)
              (5170 - 5250 @ AUTO), (N/A, 20)
              (5250 - 5330 @ 80), (N/A, 20), DFS
              (5490 - 5710 @ 80), (N/A, 27), DFS
      We will get 80MHz (5250 - 5170):
              (5170 - 5250 @ 80), (N/A, 20)
              (5250 - 5330 @ 80), (N/A, 20), DFS
      Base on this calculations we will set correct channel
      bandwidth flags (eg. IEEE80211_CHAN_NO_80MHZ).
      We don't need any changes in CRDA or internal regulatory.
      Signed-off-by: default avatarJanusz Dziedzic <janusz.dziedzic@tieto.com>
      [extend nl80211 description a bit, fix typo]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  11. 04 Feb, 2014 4 commits
    • Johannes Berg's avatar
      nl80211: fix scheduled scan RSSI matchset attribute confusion · ea73cbce
      Johannes Berg authored
      The scheduled scan matchsets were intended to be a list of filters,
      with the found BSS having to pass at least one of them to be passed
      to the host. When the RSSI attribute was added, however, this was
      broken and currently wpa_supplicant adds that attribute in its own
      matchset; however, it doesn't intend that to mean that anything
      that passes the RSSI filter should be passed to the host, instead
      it wants it to mean that everything needs to also have higher RSSI.
      This is semantically problematic because we have a list of filters
      like [ SSID1, SSID2, SSID3, RSSI ] with no real indication which
      one should be OR'ed and which one AND'ed.
      To fix this, move the RSSI filter attribute into each matchset. As
      we need to stay backward compatible, treat a matchset with only the
      RSSI attribute as a "default RSSI filter" for all other matchsets,
      but only if there are other matchsets (an RSSI-only matchset by
      itself is still desirable.)
      To make driver implementation easier, keep a global min_rssi_thold
      for the entire request as well. The only affected driver is ath6kl.
      I found this when I looked into the code after Raja Mani submitted
      a patch fixing the n_match_sets calculation to disregard the RSSI,
      but that patch didn't address the semantic issue.
      Reported-by: default avatarRaja Mani <rmani@qti.qualcomm.com>
      Acked-by: default avatarLuciano Coelho <luciano.coelho@intel.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Janusz Dziedzic's avatar
      nl80211: add Guard Interval support for set_bitrate_mask · 0b9323f6
      Janusz Dziedzic authored
      Allow to force SGI, LGI.
      Mainly for test purpose.
      Signed-off-by: default avatarJanusz Dziedzic <janusz.dziedzic@tieto.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Jouni Malinen's avatar
      cfg80211: Advertise maximum associated STAs in AP mode · b43504cf
      Jouni Malinen authored
      This allows drivers to advertise the maximum number of associated
      stations they support in AP mode (including P2P GO). User space
      applications can use this for cleaner way of handling the limit (e.g.,
      hostapd rejecting IEEE 802.11 authentication without manual
      configuration of the limit) or to figure out what type of use cases can
      be executed with multiple devices before trying and failing.
      Signed-off-by: default avatarJouni Malinen <j@w1.fi>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Jouni Malinen's avatar
      cfg80211: Allow BSS hint to be provided for connect · 1df4a510
      Jouni Malinen authored
      This clarifies the expected driver behavior on the older
      NL80211_ATTR_MAC and NL80211_ATTR_WIPHY_FREQ attributes and adds a new
      set of similar attributes with _HINT postfix to enable use of a
      recommendation of the initial BSS to choose. This can be helpful for
      some drivers that can avoid an additional full scan on connection
      request if the information is provided to them (user space tools like
      wpa_supplicant already has that information available based on earlier
      In addition, this can be used to get more expected behavior for cases
      where a specific BSS should be picked first based on operations like
      Interworking network selection or WPS. These cases were already easily
      addressed with drivers that leave BSS selection to user space, but there
      was no convenient way to do this with drivers that take care of BSS
      selection internally without using the NL80211_ATTR_MAC which is not
      really desired since it is needed for other purposes to force the
      association to remain with the same BSS.
      Signed-off-by: default avatarJouni Malinen <j@w1.fi>
      [add const, fix policy]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  12. 19 Dec, 2013 2 commits
    • Kyeyoon Park's avatar
      cfg80211: Add support for QoS mapping · fa9ffc74
      Kyeyoon Park authored
      This allows QoS mapping from external networks to be implemented as
      defined in IEEE Std 802.11-2012, 10.24.9. APs can use this to advertise
      DSCP ranges and exceptions for mapping frames to a specific UP over
      The payload of the QoS Map Set element (IEEE Std 802.11-2012,
      is sent to the driver through the new NL80211_ATTR_QOS_MAP attribute to
      configure the local behavior either on the AP (based on local
      configuration) or on a station (based on information received from the
      Signed-off-by: default avatarKyeyoon Park <kyeyoonp@qca.qualcomm.com>
      Signed-off-by: default avatarJouni Malinen <jouni@qca.qualcomm.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Johannes Berg's avatar
      nl80211: support vendor-specific events · 567ffc35
      Johannes Berg authored
      In addition to vendor-specific commands, also support vendor-specific
      events. These must be registered with cfg80211 before they can be used.
      They're also advertised in nl80211 in the wiphy information so that
      userspace knows can be expected. The events themselves are sent on a
      new multicast group called "vendor".
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  13. 16 Dec, 2013 1 commit
  14. 05 Dec, 2013 1 commit
  15. 03 Dec, 2013 2 commits
    • Johannes Berg's avatar
      nl80211: vendor command support · ad7e718c
      Johannes Berg authored
      Add support for vendor-specific commands to nl80211. This is
      intended to be used for really vendor-specific functionality
      that can't be implemented in a generic fashion for any reason.
      It's *NOT* intended to be used for any normal/generic feature
      or any optimisations that could be implemented across drivers.
      Currently, only vendor commands (with replies) are supported,
      no dump operations or vendor-specific notifications.
      Also add a function wdev_to_ieee80211_vif() to mac80211 which
      is needed for mac80211-based drivers wanting to implement any
      vendor commands.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Marek Kwaczynski's avatar
      nl80211/cfg80211: Set Operating Mode Notification · 60f4a7b1
      Marek Kwaczynski authored
      This attribute is needed for setting Operating Mode Notification
      in AP mode from User Space. This functionality is required when
      User Space received Assoc Request contains Operation Mode
      Notification element.
      Signed-off-by: default avatarMarek Kwaczynski <marek.kwaczynski@tieto.com>
      [fix typos, nl80211 documentation]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  16. 02 Dec, 2013 1 commit
  17. 25 Nov, 2013 2 commits
    • Luis R. Rodriguez's avatar
      cfg80211: consolidate passive-scan and no-ibss flags · 8fe02e16
      Luis R. Rodriguez authored
      These two flags are used for the same purpose, just
      combine them into a no-ir flag to annotate no initiating
      radiation is allowed.
      Old userspace sending either flag will have it treated as
      the no-ir flag. To be considerate to older userspace we
      also send both the no-ir flag and the old no-ibss flags.
      Newer userspace will have to be aware of older kernels.
      Update all places in the tree using these flags with the
      following semantic patch:
      -NL80211_RRF_NO_IR | NL80211_RRF_NO_IR
      -IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_NO_IR
      Along with some hand-optimisations in documentation, to
      remove duplicates and to fix some indentation.
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@do-not-panic.com>
      [do all the driver updates in one go]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Arik Nemtsov's avatar
      nl80211: better document NL80211_CMD_TDLS_MGMT · c17bff87
      Arik Nemtsov authored
      This command has different semantics depending on the action code sent.
      Document this fact and detail the supported action codes.
      Signed-off-by: default avatarArik Nemtsov <arik@wizery.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  18. 28 Oct, 2013 1 commit
  19. 11 Oct, 2013 1 commit
  20. 09 Oct, 2013 1 commit
  21. 08 Oct, 2013 1 commit
  22. 23 Aug, 2013 1 commit
  23. 01 Aug, 2013 1 commit
  24. 16 Jul, 2013 3 commits
  25. 18 Jun, 2013 1 commit
  26. 11 Jun, 2013 2 commits
  27. 29 May, 2013 1 commit