From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: How are ht-caps changes propagated after ieee80211_register_hw?
Date: Tue, 23 Sep 2014 17:23:43 -0700 [thread overview]
Message-ID: <54220F0F.4060401@candelatech.com> (raw)
In-Reply-To: <21538.3575.430682.821603@gargle.gargle.HOWL>
On 09/23/2014 05:19 PM, Sujith Manoharan wrote:
> Ben Greear wrote:
>> In ath9k, when you set the chainmask to 2x2 on a 3x3 NIC,
>> the ht-caps appear as 2-streams in station association requests.
>>
>> But, in ath10k, they still appear as 3x3. I don't see any obvious way
>> that ath9k notifies the mac80211 stack that it changed the
>> ht-caps, but it must be working somehow.
>
> In ath9k, we re-register the new HT parameters with mac80211
> when set_antenna() is called.
Yeah, I think I have it working in ath10k now, using that same
approach.
Thanks!
Ben
>
> Sujith
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2014-09-24 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 23:17 How are ht-caps changes propagated after ieee80211_register_hw? Ben Greear
2014-09-24 0:19 ` Sujith Manoharan
2014-09-24 0:23 ` Ben Greear [this message]
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=54220F0F.4060401@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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).