* How are ht-caps changes propagated after ieee80211_register_hw?
@ 2014-09-23 23:17 Ben Greear
2014-09-24 0:19 ` Sujith Manoharan
0 siblings, 1 reply; 3+ messages in thread
From: Ben Greear @ 2014-09-23 23:17 UTC (permalink / raw)
To: linux-wireless@vger.kernel.org
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.
Anyone know the proper way this information should make it
into the mac80211 layer?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How are ht-caps changes propagated after ieee80211_register_hw?
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
0 siblings, 1 reply; 3+ messages in thread
From: Sujith Manoharan @ 2014-09-24 0:19 UTC (permalink / raw)
To: Ben Greear; +Cc: linux-wireless@vger.kernel.org
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.
Sujith
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How are ht-caps changes propagated after ieee80211_register_hw?
2014-09-24 0:19 ` Sujith Manoharan
@ 2014-09-24 0:23 ` Ben Greear
0 siblings, 0 replies; 3+ messages in thread
From: Ben Greear @ 2014-09-24 0:23 UTC (permalink / raw)
To: Sujith Manoharan; +Cc: linux-wireless@vger.kernel.org
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-09-24 0:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).