1. 29 8月, 2014 1 次提交
  2. 16 7月, 2014 1 次提交
  3. 26 6月, 2014 1 次提交
  4. 08 5月, 2014 1 次提交
  5. 15 3月, 2014 1 次提交
  6. 01 3月, 2014 1 次提交
  7. 13 2月, 2014 6 次提交
  8. 09 1月, 2014 1 次提交
  9. 19 12月, 2013 3 次提交
  10. 10 12月, 2013 1 次提交
  11. 12 11月, 2013 1 次提交
  12. 11 10月, 2013 1 次提交
  13. 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
  14. 24 7月, 2013 1 次提交
  15. 23 5月, 2013 1 次提交
  16. 26 3月, 2013 1 次提交
  17. 07 3月, 2013 2 次提交
  18. 19 2月, 2013 1 次提交
  19. 08 1月, 2013 1 次提交
  20. 29 9月, 2012 5 次提交
  21. 08 9月, 2012 1 次提交
  22. 11 8月, 2012 1 次提交
  23. 07 8月, 2012 2 次提交
  24. 18 7月, 2012 1 次提交
    • A
      mwifiex: remove redundant code in set channel path · 1f45b39e
      Amitkumar Karwar 提交于
      1) Recently we removed set_channel cfg80211 handler. Also, cfg80211
      blocks ibss connection requests if ibss network is already started
      /joined. Hence the code to restart ibss network in new channel
      (mwifiex_drv_change_adhoc_chan() function) becomes redundant.
      
      2) mwifiex_bss_set_channel() function is redundant. It does some
      error checking and calculate adhoc start band and adhoc channel.
      Cfg80211 already takes care of error checking and provides correct
      channel information to the driver. Adhoc start band is already
      calculated in mwifiex_set_rf_channel() function.
      
      Other associated code is also removed in this patch.
      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>
      1f45b39e
  25. 10 7月, 2012 1 次提交
  26. 29 6月, 2012 1 次提交