Any idea why we cannot disable /b rates?

Ben Greear greearb at
Tue Feb 24 11:44:02 PST 2015

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?


On 02/24/2015 09:43 AM, Ben Greear wrote:
> I'm going to start digging into the code, but in case someone already
> knows...
> I ran this command to try to disable any frames set at /b rates (AP is on channel 1).
> But, according to ath10k sniffer, beacons are still sent with 1Mbps rate.
> iw dev vap1 set bitrates legacy-2.4 12 mcs-2.4
> Thanks,
> Ben

Ben Greear <greearb at>
Candela Technologies Inc

More information about the ath10k mailing list