1. 29 1月, 2016 1 次提交
  2. 18 11月, 2015 1 次提交
  3. 08 6月, 2015 1 次提交
  4. 26 5月, 2015 2 次提交
  5. 07 1月, 2015 2 次提交
  6. 26 6月, 2014 1 次提交
  7. 23 4月, 2014 1 次提交
  8. 15 3月, 2014 1 次提交
  9. 01 3月, 2014 1 次提交
  10. 13 2月, 2014 4 次提交
  11. 10 8月, 2013 2 次提交
    • A
      mwifiex: add packet coalesce support · 562fc5b3
      Amitkumar Karwar 提交于
      Coalesce filters are configured in firmware based on settings
      received from cfg80211.
      
      Packet type which is required by firmware is determined based on
      provided patterns in a rule:
      
      Unicast: if pattern '01' with offset 0 is found
      Multicast: if pattern '33:33' or '01:00:5e' with offset 0 is found
      Broadcast: if pattern 'ff:ff:ff:ff' with offset 0 is found
      
      Some example coalesce configuration files:
      
      1) Coalesce Rx data packets from 192.168.0.88
      mac address of our device is 00:50:43:21:53:7A
      Source IP address offset comes out as 52 after following
      calculations:
          32 bytes of HW 802.11 header + 8 bytes LLC +
          12 bytes in IPV4 header till source IP address
      Destination mac is at offset 6 in HW header.
      
      delay=100
      condition=1
      patterns=01,6+00:50:43:22,10+53:7A,52+c0:a8:00:58
      
      2) Coalesce all broadcast and multicast packets(Multiple packet
      types are not allowed in a single rule. Hence created separate
      rules)
      
      delay=400
      condition=1
      patterns=33:33
      delay=400
      condition=1
      patterns=ff:ff:ff:ff
      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>
      562fc5b3
    • A
      mwifiex: rename mef macros · 3f4e854a
      Amitkumar Karwar 提交于
      Their names were generic. We need to define similar macros
      for coalesce feature. Hence they are renamed here.
      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>
      3f4e854a
  12. 26 3月, 2013 1 次提交
  13. 07 3月, 2013 1 次提交
    • 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
  14. 19 2月, 2013 1 次提交
  15. 02 2月, 2013 1 次提交
  16. 08 1月, 2013 1 次提交
  17. 29 9月, 2012 1 次提交
  18. 08 9月, 2012 1 次提交
  19. 07 8月, 2012 2 次提交
  20. 18 7月, 2012 1 次提交
  21. 10 7月, 2012 1 次提交
  22. 21 6月, 2012 2 次提交
  23. 17 5月, 2012 5 次提交
  24. 13 4月, 2012 2 次提交
  25. 10 4月, 2012 2 次提交
  26. 06 3月, 2012 1 次提交