From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Re: Any idea why we cannot disable /b rates?
Date: Tue, 24 Feb 2015 11:44:02 -0800 [thread overview]
Message-ID: <54ECD482.3060003@candelatech.com> (raw)
In-Reply-To: <54ECB852.3030208@candelatech.com>
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?
Thanks,
Ben
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@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-02-24 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:43 Any idea why we cannot disable /b rates? Ben Greear
2015-02-24 19:44 ` Ben Greear [this message]
2015-02-25 2:45 ` Yeoh Chun-Yeow
2015-02-25 5:02 ` Ben Greear
2015-02-25 10:30 ` Yeoh Chun-Yeow
2015-02-25 23:25 ` Ben Greear
2015-03-10 23:59 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54ECD482.3060003@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox