Skip to content
Snippets Groups Projects
Select Git revision
  • 0x4A6F-rpi4
  • 0x4A6F-master
  • master
  • v2018.2.2-ffs
  • v2018.2.x default protected
  • v2016.2.4-batmanbug
  • radv-filterd
  • v2016.2.x
  • hoodselector
  • v2016.1.x
  • babel
  • v2015.1.x
  • 2014.4.x
  • 2014.3.x
  • v2018.2.2-ffs0.1
  • v2018.2.1-ffs0.1
  • v2018.2.1
  • v2018.2-ffs0.1
  • v2018.2
  • v2018.1.4
  • v2018.1.3
  • v2018.1.2
  • v2018.1.1
  • v2018.1
  • v2017.1.8
  • v2017.1.7
  • v2017.1.6
  • v2017.1.5
  • v2017.1.4
  • v2017.1.3
  • v2017.1.2
  • v2016.2.7
  • v2017.1.1
  • v2017.1
34 results

0019-ath10k-ct-fix-incorrect-multicast-broadcast-rate-setting.patch

Blame
  • Forked from firmware / FFS Gluon
    2518 commits behind the upstream repository.
    • Sven Eckelmann's avatar
      b2f249e9
      ath10k/ath10k-ct: fix incorrect multicast/broadcast rate setting · b2f249e9
      Sven Eckelmann authored
      If no mcast_rate is set for the wifi-iface then there is no rate_idx (0)
      set for the bss. This breaks 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: a399b607 ("ath10k/ath10k-ct: support multicast and management rate control")
      b2f249e9
      History
      ath10k/ath10k-ct: fix incorrect multicast/broadcast rate setting
      Sven Eckelmann authored
      If no mcast_rate is set for the wifi-iface then there is no rate_idx (0)
      set for the bss. This breaks 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: a399b607 ("ath10k/ath10k-ct: support multicast and management rate control")
    0019-ath10k-ct-fix-incorrect-multicast-broadcast-rate-setting.patch 4.76 KiB