1. 05 2月, 2014 1 次提交
  2. 24 1月, 2014 1 次提交
  3. 17 1月, 2014 1 次提交
  4. 09 1月, 2014 1 次提交
  5. 19 12月, 2013 2 次提交
  6. 10 12月, 2013 1 次提交
  7. 05 12月, 2013 1 次提交
  8. 02 12月, 2013 1 次提交
  9. 26 11月, 2013 2 次提交
    • L
      cfg80211: move regulatory flags to their own variable · a2f73b6c
      Luis R. Rodriguez 提交于
      We'll expand this later, this will make it easier to
      classify and review what things are related to regulatory
      or not.
      
      Coccinelle only missed 4 hits, which I had to do manually,
      supplying the SmPL in case of merge conflicts.
      
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags |= WIPHY_FLAG_CUSTOM_REGULATORY
      +wiphy->regulatory_flags |= REGULATORY_CUSTOM_REG
      @@
      expression e;
      @@
      -e->flags |= WIPHY_FLAG_CUSTOM_REGULATORY
      +e->regulatory_flags |= REGULATORY_CUSTOM_REG
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags &= ~WIPHY_FLAG_CUSTOM_REGULATORY
      +wiphy->regulatory_flags &= ~REGULATORY_CUSTOM_REG
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags & WIPHY_FLAG_CUSTOM_REGULATORY
      +wiphy->regulatory_flags & REGULATORY_CUSTOM_REG
      
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags |= WIPHY_FLAG_STRICT_REGULATORY
      +wiphy->regulatory_flags |= REGULATORY_STRICT_REG
      @@
      expression e;
      @@
      -e->flags |= WIPHY_FLAG_STRICT_REGULATORY
      +e->regulatory_flags |= REGULATORY_STRICT_REG
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags &= ~WIPHY_FLAG_STRICT_REGULATORY
      +wiphy->regulatory_flags &= ~REGULATORY_STRICT_REG
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags & WIPHY_FLAG_STRICT_REGULATORY
      +wiphy->regulatory_flags & REGULATORY_STRICT_REG
      
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags |= WIPHY_FLAG_DISABLE_BEACON_HINTS
      +wiphy->regulatory_flags |= REGULATORY_DISABLE_BEACON_HINTS
      @@
      expression e;
      @@
      -e->flags |= WIPHY_FLAG_DISABLE_BEACON_HINTS
      +e->regulatory_flags |= REGULATORY_DISABLE_BEACON_HINTS
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags &= ~WIPHY_FLAG_DISABLE_BEACON_HINTS
      +wiphy->regulatory_flags &= ~REGULATORY_DISABLE_BEACON_HINTS
      @@
      struct wiphy *wiphy;
      @@
      -wiphy->flags & WIPHY_FLAG_DISABLE_BEACON_HINTS
      +wiphy->regulatory_flags & REGULATORY_DISABLE_BEACON_HINTS
      
      Generated-by: Coccinelle SmPL
      Cc: Julia Lawall <julia.lawall@lip6.fr>
      Cc: Peter Senna Tschudin <peter.senna@gmail.com>
      Cc: Mihir Shete <smihir@qti.qualcomm.com>
      Cc: Henri Bahini <hbahini@qca.qualcomm.com>
      Cc: Tushnim Bhattacharyya <tushnimb@qca.qualcomm.com>
      Signed-off-by: NLuis R. Rodriguez <mcgrof@do-not-panic.com>
      [fix up whitespace damage, overly long lines]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      a2f73b6c
    • L
      cfg80211: consolidate passive-scan and no-ibss flags · 8fe02e16
      Luis R. Rodriguez 提交于
      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_PASSIVE_SCAN
      +NL80211_RRF_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IBSS
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_PASSIVE_SCAN
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IBSS
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IR | NL80211_RRF_NO_IR
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_NO_IR
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -(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: NLuis R. Rodriguez <mcgrof@do-not-panic.com>
      [do all the driver updates in one go]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8fe02e16
  10. 16 11月, 2013 2 次提交
  11. 27 8月, 2013 1 次提交
  12. 13 8月, 2013 1 次提交
  13. 10 8月, 2013 3 次提交
  14. 01 8月, 2013 1 次提交
  15. 24 7月, 2013 3 次提交
  16. 16 7月, 2013 1 次提交
  17. 18 6月, 2013 1 次提交
  18. 04 6月, 2013 1 次提交
  19. 23 5月, 2013 2 次提交
  20. 09 5月, 2013 1 次提交
  21. 08 5月, 2013 1 次提交
  22. 23 4月, 2013 3 次提交
  23. 02 4月, 2013 2 次提交
  24. 26 3月, 2013 1 次提交
  25. 19 3月, 2013 1 次提交
  26. 09 3月, 2013 1 次提交
  27. 07 3月, 2013 2 次提交
    • A
      mwifiex: add WOWLAN support · 7da060c1
      Amitkumar Karwar 提交于
      Currently 'magic-packet' and 'patterns' options in 'iw wowlan'
      command are supported.
      
      Appropriate packet filters for wowlan are configured in firmware
      based on provided patterns and/or magic-packet option.
      
      For examples,
      
      wake-on ARP request for 192.168.0.100:
      iw phy0 wowlan enable patterns ff:ff:ff:ff:ff:ff 20+08:06
        46+c0:a8:00:64
      
      wake-on RX packets sent from IP address 192.168.0.88:
      iw phy0 wowlan enable patterns 34+c0:a8:00:58
      
      wake-on RX packets with TCP destination port 80
      iw phy0 wowlan enable patterns 44+50
      
      wake-on MagicPacket:
      iw phy0 wowlan enable magic-packet
      
      wake-on MagicPacket or patterns:
      iw phy0 wowlan enable magic-packet patterns 12+00:11:22:33:44:55
        18+00:50:43:21
      
      wake-on IPv4 multicast packets:
      iw phy0 wowlan enable patterns 01:00:5e
      
      wake-on IPv6 multicast packets:
      iw phy0 wowlan enable patterns 33:33
      
      disable all wowlan options
      iw phy0 wowlan disable
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NBing Zhao <bzhao@marvell.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      7da060c1
    • A
      mwifiex: add "ethtool wol" command support · 0d7f53e3
      Amitkumar Karwar 提交于
      Host sleep wakeup condition is configured using this command.
      
      Supports Wake-on: pumb
      
      For examples:
      
      wake-on any unicast packets:
      ethtool -s mlan0 wol u
      
      wake-on multicast/broadcast packet:
      ethtool -s mlan0 wol mb
      
      wake-on unicast packets and MAC events:
      ethtool -s mlan0 wol pu
      
      wake-on unicast/multicast/broadcast packets and MAC events:
      ethtool -s mlan0 wol pmbu
      
      disable all wake-on options:
      ethtool -s mlan0 wol d
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NBing Zhao <bzhao@marvell.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      0d7f53e3
  28. 19 2月, 2013 1 次提交