1. 24 4月, 2014 1 次提交
  2. 08 4月, 2014 1 次提交
  3. 24 3月, 2014 1 次提交
  4. 11 3月, 2014 1 次提交
  5. 07 3月, 2014 1 次提交
  6. 28 2月, 2014 1 次提交
  7. 13 2月, 2014 2 次提交
  8. 30 1月, 2014 1 次提交
    • M
      ath10k: configure access category for arp · ab6258ed
      Marek Puzyniak 提交于
      ARP frames exchange does not work properly for UAPSD enabled AP.
      ARP requests which arrives with access category 0 are processed
      by network stack and send back with access category 0. FW changes
      access category to 6. This is causing problems when UAPSD associated
      STA is sleeping after has sent ARP request. Configure ARP access
      category in FW to best effort (0) solves this problem. ARP frames
      will be send with access category 0.
      
      Simplify arp ac override functionality by removing redundant entry in
      pdev param maping table. There should be only one entry in pdev param
      map but enum has different name for different FW.
      
      kvalo: change the warning message
      Signed-off-by: NMarek Puzyniak <marek.puzyniak@tieto.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      ab6258ed
  9. 24 1月, 2014 2 次提交
  10. 23 1月, 2014 1 次提交
    • K
      ath10k: enable firmware STA quick kickout · 5a13e76e
      Kalle Valo 提交于
      Firmware has a feature to track if the associated STA is not acking the frames.
      When that happens, the firmware sends WMI_PEER_STA_KICKOUT_EVENTID event to the
      host. Enable that to faster detect when a STA has left BSS without sending a
      deauth frame.
      
      Also set huge keepalive timeouts to avoid using the keepalive functionality in
      the firmware.
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      5a13e76e
  11. 20 1月, 2014 1 次提交
  12. 10 1月, 2014 3 次提交
  13. 16 12月, 2013 1 次提交
  14. 11 12月, 2013 1 次提交
  15. 20 11月, 2013 3 次提交
  16. 30 10月, 2013 2 次提交
  17. 21 10月, 2013 1 次提交
  18. 16 10月, 2013 4 次提交
  19. 07 10月, 2013 2 次提交
  20. 03 10月, 2013 2 次提交
  21. 01 10月, 2013 1 次提交
    • K
      ath10k: implement firmware IE container support · 1a222435
      Kalle Valo 提交于
      Firmware IE containers can dynamically provide various information what
      firmware supports. Also it can embed more than one image so updating firmware
      is easy, user just needs to update one file in /lib/firmware/.
      
      The firmware API 2 or higher will use the IE container format, the current API
      1 will not use the new format but it still is supported for some time. FW API 2
      files are named as firmware-2.bin (which contains both firmware and otp images)
      and API 1 files are firmware.bin and otp.bin.
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      1a222435
  22. 27 9月, 2013 7 次提交