1. 11 Jun, 2019 2 commits
  2. 13 Jun, 2018 1 commit
  3. 18 Nov, 2017 1 commit
  4. 18 Oct, 2017 1 commit
  5. 12 Oct, 2017 1 commit
  6. 21 Jul, 2017 1 commit
  7. 31 Oct, 2016 1 commit
  8. 22 Oct, 2016 1 commit
  9. 21 Oct, 2015 6 commits
  10. 29 Sep, 2015 7 commits
  11. 25 Aug, 2015 3 commits
  12. 21 Jul, 2015 1 commit
    • Rafa? Mi?ecki's avatar
      brcmfmac: set wiphy's addresses to provide valid MACs · e3faa866
      Rafa? Mi?ecki authored
      
      
      Broadcom's firmware requires every BSS to use MAC address with unique
      last few bits. The amount of bits may depend on a particular firmware,
      it was verified to be 2 for BCM43602 one.
      If this condition won't be fulfilled firmware will reject such MAC:
      brcmfmac: _brcmf_set_mac_address: Setting cur_etheraddr failed, -52
      
      We don't want to simply set addr_mask as it would also disallow using
      locally administrated bit. Instead let's build a list of addresses
      manually enabling 0x2 bit for extra interfaces.
      Signed-off-by: default avatarRafa? Mi?ecki <zajec5@gmail.com>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
      e3faa866
  13. 15 Jun, 2015 3 commits
  14. 08 Jun, 2015 1 commit
  15. 26 May, 2015 1 commit
    • Johannes Berg's avatar
      cfg80211: properly send NL80211_ATTR_DISCONNECTED_BY_AP in disconnect · 80279fb7
      Johannes Berg authored
      
      
      When we disconnect from the AP, drivers call cfg80211_disconnect().
      This doesn't know whether the disconnection was initiated locally
      or by the AP though, which can cause problems with the supplicant,
      for example with WPS. This issue obviously doesn't show up with any
      mac80211 based driver since mac80211 doesn't call this function.
      
      Fix this by requiring drivers to indicate whether the disconnect is
      locally generated or not. I've tried to update the drivers, but may
      not have gotten the values correct, and some drivers may currently
      not be able to report correct values. In case of doubt I left it at
      false, which is the current behaviour.
      
      For libertas, make adjustments as indicated by Dan Williams.
      Reported-by: default avatarMatthieu Mauger <matthieux.mauger@intel.com>
      Tested-by: default avatarMatthieu Mauger <matthieux.mauger@intel.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      80279fb7
  16. 09 May, 2015 3 commits
  17. 30 Mar, 2015 1 commit
    • Tom Gundersen's avatar
      cfg80211: pass name_assign_type to rdev_add_virtual_intf() · 6bab2e19
      Tom Gundersen authored
      This will expose in /sys whether the ifname of a device is set by
      userspace or generated by the kernel. The latter kind (wlanX, etc)
      is not deterministic, so userspace needs to rename these devices
      to names that are guaranteed to stay the same between reboots. The
      former, however should never be renamed, so userspace needs to be
      able to reliably tell the difference.
      
      Similar functionality was introduced for the rtnetlink core in
      commit 5517750f
      
       ("net: rtnetlink - make create_link take name_assign_type")
      Signed-off-by: default avatarTom Gundersen <teg@jklm.no>
      Cc: Kalle Valo <kvalo@qca.qualcomm.com>
      Cc: Brett Rudley <brudley@broadcom.com>
      Cc: Arend van Spriel <arend@broadcom.com>
      Cc: Franky (Zhenhui) Lin <frankyl@broadcom.com>
      Cc: Hante Meuleman <meuleman@broadcom.com>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      [reformat changelog to fit 72 cols]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      6bab2e19
  18. 03 Mar, 2015 1 commit
  19. 02 Mar, 2015 1 commit
  20. 26 Feb, 2015 2 commits
  21. 29 Jan, 2015 1 commit