mirror of
git://git.openwrt.org/openwrt/openwrt.git
synced 2025-10-28 20:44:27 -04:00
ba249bc955
If no mcast_rate is set for the wifi-iface then there is no rate_idx (0)
set for the bss. This can break for example 5GHz meshpoint interfaces
because 0 maps to a CCK rate (11Mbit/s).
It must also be avoided that the ath10k-ct internal state for the rates is
not synced with the mac80211 rates state. Otherwise, the user specified
rate (e.g. a wifi-iface mcast_rate for a meshpoint interface) will only be
set on startup. And a short while after that, ath10k-ct specific code in
ath10k_check_apply_special_rates is missing a valid rate in its own
structures and is then recalculating a new default rate. This default rate
is in most situations not the requested rate.
Fixes:
|
||
|---|---|---|
| .. | ||
| 081-ath10k-calibration-variant.patch | ||
| 100-kernel_compat.patch | ||
| 110-api_fix.patch | ||
| 120-mac80211-4-14-api.patch | ||
| 160-ath10k-search-all-IEs-for-variant-before-falling-back.patch | ||
| 161-ath10k-add-support-for-configuring-management-packet.patch | ||
| 162-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch | ||
| 163-ath10k-fix-incorrect-multicast-broadcast-rate-settin.patch | ||
| 164-ath10k-commit-rates-from-mac80211.patch | ||
| 200-ath10k-move-spectral-scan-support-under-a-separate-c.patch | ||
| 201-ath10k-4.16_add-LED-and-GPIO-controlling-support-for-various-chipsets.patch | ||
| 202-ath10k-4.16-use-tpt-trigger-by-default.patch | ||