From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Allowing station to over-ride default VHT-oper element?
Date: Wed, 10 Jun 2015 12:29:32 -0700 [thread overview]
Message-ID: <5578901C.60502@candelatech.com> (raw)
I'm trying to figure out how to make a VHT station with hardware capable
of 80Mhz width instead force itself to advertise/use just 40Mhz width,
but still support VHT.
Similar to how the VHT-capabilities overrides works, but for
VHT-operation.
First, is this even a valid thing to do, or does VHT imply
that stations are always available to do 80Mhz?
And second, if it is a valid thing to do, any hints on a
proper way to go about this. I'm getting a bit tangled in
the code trying to figure out where to apply any overloads
properly.
Possibly in ieee80211_determine_chantype?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-06-10 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 19:29 Ben Greear [this message]
2015-06-10 19:55 ` Allowing station to over-ride default VHT-oper element? Johannes Berg
2015-06-10 19:58 ` Ben Greear
2015-06-10 20:01 ` Johannes Berg
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=5578901C.60502@candelatech.com \
--to=greearb@candelatech.com \
--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).