Any idea why we cannot disable /b rates?

Yeoh Chun-Yeow yeohchunyeow at
Tue Feb 24 18:45:27 PST 2015

On Wed, Feb 25, 2015 at 3:44 AM, Ben Greear <greearb at> wrote:
> Ok, so I found the problem.  Appears that the firmware uses two different
> fixed rate-ctrl settings, one for non-data (bcast, mgt-frames, etc) and another
> for data frames.  The non-data one was not being set when user configured
> fixed rates, so beacons went out at 1Mbps.
> I updated CT firmware (beta-14) to set both data and non-data to the same
> value when the driver specifies the rates...  Seems to work...any idea
> if this is a bad idea in practice?

Rate control is applicable to unicast frame whether it is
management/data. Broadcast/Multicast rate is required for
management/data (usually the lowest transmission rate 5GHz is 6Mbps).

So it is more sensible if we can configure the broadcast/multicast
rate and also disable the rate control for unicast frame by using
fixed rate.


More information about the ath10k mailing list