1. 13 2月, 2014 1 次提交
  2. 24 1月, 2014 2 次提交
  3. 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
  4. 10 1月, 2014 3 次提交
  5. 16 12月, 2013 1 次提交
  6. 20 11月, 2013 4 次提交
  7. 15 11月, 2013 1 次提交
  8. 16 10月, 2013 2 次提交
  9. 01 10月, 2013 3 次提交
  10. 27 9月, 2013 5 次提交
  11. 20 9月, 2013 2 次提交
  12. 17 9月, 2013 4 次提交
  13. 06 9月, 2013 1 次提交
  14. 03 9月, 2013 1 次提交
    • K
      ath10k: check chip id from the soc register during probe · e01ae68c
      Kalle Valo 提交于
      ath10k doesn't support qca988x hw1.0 boards anymore. Unfortunately
      the PCI id is the same in hw1.0 and hw2.0 so ath10k tries to use
      hw1.0 boards anyway. But without hw1.0 workarounds in place
      ath10k just crashes horribly.
      
      To avoid using hw1.0 boards at all add a chip id detection
      and fail the probe if hw1.0 is detected:
      
      [ 5265.786408] ath10k: ERROR: qca988x hw1.0 is not supported
      [ 5265.786497] ath10k: Unsupported chip id 0x043200ff
      [ 5265.786574] ath10k: could not register driver core (-95)
      [ 5265.793191] ath10k_pci: probe of 0000:02:00.0 failed with error -95
      
      Also add a warning if there's an unknown chip id but continue
      the boot process normally anyway.
      Reported-by: NZaki Bakar <zaki.bm@gmail.com>
      Tested-by: NChristian Lamparter <chunkeey@googlemail.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      e01ae68c
  15. 15 8月, 2013 1 次提交
  16. 02 8月, 2013 1 次提交
  17. 31 7月, 2013 1 次提交
  18. 30 7月, 2013 6 次提交