How are ht-caps changes propagated after ieee80211_register_hw?
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
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 6 lines · Ben Greear
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
Quoted 10 lines · Sujith Manoharan
Quoted 6 lines · Ben Greear
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
Quoted 3 lines
Sujith
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com