From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: CT firmware beta-15 can now configure arbitrary rate-sets.
Date: Tue, 15 Sep 2015 17:56:11 -0700 [thread overview]
Message-ID: <55F8BE2B.7030004@candelatech.com> (raw)
Here is the changelog note. This requires some corresponding driver patchs to
enable configuring the rateset (and fetching the tx-ratectrl memory from the host)
I tested this on my 4.0.4+ kernel.
Should be useful for anyone trying make a station transmit in pure /b mode.
And, likely could help tune various other ratesets as well. So far, the ath10k
driver patches do not enable HT or VHT filters, but I hope to add that soon.
If all goes according to plan, the firmware will just magically work for HT and
VHT ratemasks.
Some of the ath10k driver patches probably help/work-with upstream firmware as well,
but I don't have time to deal with dis-entangling it from my CT specific changes.
If someone else wants to do so, please be my guest.
* Allow setting arbitrary rate-mask. This allows the user to disable all but
/b legacy rates, for instance. It should also allow configuring subsets of
all other HT and VHT rates, but that has not yet been tested.
In addition, fix several bugs that caused the firmware to ignore tx-rate-ctrl
settings because it did not properly fetch the cached RAM from the host OS.
To enable these features, you need to be using the CT kernel patches (currently
only in 4.0, but will at least be ported forward to 4.2 sometime soon. Might
not be ported to 3.17 or other older kernels.)
http://www.candelatech.com/ath10k.php
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-4.0.dev.y/.git;a=summary
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2015-09-16 0:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55F8BE2B.7030004@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).