1. 28 Sep, 2011 4 commits
  2. 27 Sep, 2011 4 commits
  3. 23 Sep, 2011 2 commits
    • Vasanthakumar Thiagarajan's avatar
      ath6kl: Fix disconnect event reporting · 1de547d6
      Vasanthakumar Thiagarajan authored
      Driver does not report disconnect event properly when in connecting state,
      this leads to issues failures in starting reconnection. Send a disconnect
      command to target when a disconnect event is received with reason code
      other than 3 (DISCONNECT_CMD - disconnect request from host) to make the
      frimware stop trying to connect even after giving disconnect event. There
      will be one more disconnect event for this disconnect command with reason
      code DISCONNECT_CMD which will be notified to cfg80211.
      Signed-off-by: default avatarVasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
      Signed-off-by: default avatarKalle Valo <kvalo@qca.qualcomm.com>
      1de547d6
    • Kalle Valo's avatar
      ath6kl: pass only unicast frames for aggregation · 5694f962
      Kalle Valo authored
      When pinging form ar6003 to the AP RTT was high even when power save was
      disabled:
      
      100 packets transmitted, 97 received, 3% packet loss, time 99125ms
      rtt min/avg/max/mdev = 1.875/46.733/795.506/139.181 ms
      
      After some investigation one reason for this was that received
      multicast traffic confused the aggrecation logic and caused 400 ms
      timeouts when receiving multicast frames from AP.
      
      A simple way to fix is to pass only unicast frames for aggregation. This
      improves RTT:
      
      100 packets transmitted, 99 received, 1% packet loss, time 99144ms
      rtt min/avg/max/mdev = 2.083/13.084/403.390/56.794 ms
      Signed-off-by: default avatarKalle Valo <kvalo@qca.qualcomm.com>
      5694f962
  4. 22 Sep, 2011 12 commits
  5. 21 Sep, 2011 13 commits
  6. 20 Sep, 2011 5 commits