ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: David Bauer <mail@david-bauer.net>, ath10k@lists.infradead.org
Subject: Re: Management rate-control on IPQ4019
Date: Tue, 18 Feb 2020 11:58:43 -0800	[thread overview]
Message-ID: <5E4C41F3.2000500@candelatech.com> (raw)
In-Reply-To: <20543d04-7847-8a4f-7882-78c2f42c98c0@david-bauer.net>

On 02/18/2020 11:12 AM, David Bauer wrote:
> Hello,
>
> while playing around with the 2.4GHz WiFi part of the IPQ4019, i was
> expecting being able to set the rate at which IPQ4019 transmits it's beacon
> frames.
>
> Using OpenWrt, setting "legacy_rates=0" on the radio leads to only advertising
> 802.11g speeds, however the beacons are still sent out at 1 Mbit/s. Using a QCA9984,
> the beacons are correctly sent out at the lowest 802.11g rate (6 Mbit/s). So i assume
> this is either a bug in the ath10k firmware or a hardware-shortcoming. Has anyone else
> experienced this bug and is it likely we'll see it fixed in a later firmware release?
>
> Hardware: IPQ4029 (Aruba AP-303)
> Firmware  Version: 10.4-3.6-00140 / 10.4-3.5.3-00078

There are separate API for setting management frame rates.  I forget exactly how
upstream supports this, but maybe check debugfs?

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

  reply	other threads:[~2020-02-18 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 19:12 Management rate-control on IPQ4019 David Bauer
2020-02-18 19:58 ` Ben Greear [this message]
2020-02-18 23:06   ` David Bauer
2020-02-19 10:29     ` Ben Greear
2020-02-19 22:05       ` David Bauer

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=5E4C41F3.2000500@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=mail@david-bauer.net \
    /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