Hi Felix,
On 6/23/23 12:47, Felix Fietkau wrote:
On 23.06.23 12:29, David Bauer wrote:
Hi Felix,
On 6/23/23 08:55, Felix Fietkau wrote:
On 18.05.23 11:19, David Bauer wrote:
ath10k does not report excessive loss in case of broken block-ack
sessions. The loss is communicated to the host-os,
On 23.06.23 12:29, David Bauer wrote:
Hi Felix,
On 6/23/23 08:55, Felix Fietkau wrote:
On 18.05.23 11:19, David Bauer wrote:
ath10k does not report excessive loss in case of broken block-ack
sessions. The loss is communicated to the host-os, but ath10k does not
trigger a low-ack events by
Hi Felix,
On 6/23/23 08:55, Felix Fietkau wrote:
On 18.05.23 11:19, David Bauer wrote:
ath10k does not report excessive loss in case of broken block-ack
sessions. The loss is communicated to the host-os, but ath10k does not
trigger a low-ack events by itself.
The mac80211 framework for loss
On 18.05.23 11:19, David Bauer wrote:
ath10k does not report excessive loss in case of broken block-ack
sessions. The loss is communicated to the host-os, but ath10k does not
trigger a low-ack events by itself.
The mac80211 framework for loss detection however detects this
circumstance well in
/subsys/340-mac80211-always-use-mac80211-loss-detection.patch
@@ -0,0 +1,33 @@
+From cdf461888f900c3a149b10a04d72b4a590ecdec3 Mon Sep 17 00:00:00 2001
+From: David Bauer
+Date: Tue, 16 May 2023 23:11:32 +0200
+Subject: [PATCH] mac80211: always use mac80211 loss detection
+
+ath10k does not report
