aboutsummaryrefslogtreecommitdiffstats
path: root/package/kernel/rtc-rv5c386a
diff options
context:
space:
mode:
authorKoen Vandeputte <koen.vandeputte@ncentric.com>2019-08-28 12:12:41 +0200
committerKoen Vandeputte <koen.vandeputte@ncentric.com>2019-08-28 13:08:21 +0200
commit5cc942a80eff3b41df164d5e875befa4fc12b183 (patch)
tree32c4dd126d6ab14a27cd043af60ed75bdd766adc /package/kernel/rtc-rv5c386a
parent1bc31e0339352839780a2bb01c350e103f757d72 (diff)
downloadupstream-5cc942a80eff3b41df164d5e875befa4fc12b183.tar.gz
upstream-5cc942a80eff3b41df164d5e875befa4fc12b183.tar.bz2
upstream-5cc942a80eff3b41df164d5e875befa4fc12b183.zip
ath9k: backport dynack improvements
Close cooperation with Lorenzo Bianconi resulted in these patches which fix all remaining seen issues when using dynack. Fix link losses when: - Late Ack's are not seen or not present - switching from too low static coverage class to dynack on a live link These are fixed by setting the Ack Timeout/Slottime to the max possible value for the currently used channel width when a new station has been discovered. When traffic flows, dynack is able to adjust to optimal values within a few packets received (typically < 1 second) These changes have been thoroughly tested on ~60 offshore devices all interconnected using mesh over IBSS and dynack enabled on all. Distances between devices varied from <100m up to ~35km Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
Diffstat (limited to 'package/kernel/rtc-rv5c386a')
0 files changed, 0 insertions, 0 deletions