From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 1/2] wireless: Support ht-capabilities over-rides.
Date: Mon, 07 Nov 2011 08:27:03 -0800 [thread overview]
Message-ID: <4EB806D7.6050104@candelatech.com> (raw)
In-Reply-To: <1320656776.3993.21.camel@jlt3.sipsolutions.net>
On 11/07/2011 01:06 AM, Johannes Berg wrote:
> On Fri, 2011-11-04 at 13:10 -0700, greearb@candelatech.com wrote:
>
>> + * @NL80211_ATTR_DISABLE_HT: Force HT capable interfaces to disable
>> + * this feature.
>
> I can see this, but
>
>> + * @NL80211_ATTR_DISABLE_HT40: Disable HT-40 even if AP and hardware
>> + * support it.
>> + * @NL80211_ATTR_HT_CAPABILITY_MASK: Specify which bits of the HT_CAPs
>> + * to pay attention to.
>
> if you have the mask why do you still need the HT40? Isn't HT40 a flag
> in the mask? Or do you want this to affect TX/RX separately? You should
> spell that out more explicitly then.
I think it would work to just use the mask & ht-cap overrides to disable HT40.
I'll see if I can get that working properly.
>
>> --- a/net/wireless/core.c
>> +++ b/net/wireless/core.c
>> @@ -704,6 +704,9 @@ void wiphy_unregister(struct wiphy *wiphy)
>> flush_work(&rdev->scan_done_wk);
>> cancel_work_sync(&rdev->conn_work);
>> flush_work(&rdev->event_work);
>> +
>> + kfree(rdev->wiphy.ht_capa_mod_mask);
>> + rdev->wiphy.ht_capa_mod_mask = NULL;
>
> That doesn't seem right -- drivers should typically assign a static
> const variable to this pointer that can't be freed.
Earlier I think you argued that all of mac80211 drivers automatically supported
these features as long as I put in the limitations that certain values
could only be increased and certain only decreased, etc.
So, I put it in the mac80211 code instead of down in the drivers.
But, I can move it into ath9k if you prefer.
>> @@ -537,6 +539,12 @@ int __cfg80211_mlme_assoc(struct cfg80211_registered_device *rdev,
>> memcpy(&req.crypto, crypt, sizeof(req.crypto));
>> req.use_mfp = use_mfp;
>> req.prev_bssid = prev_bssid;
>> + req.flags = assoc_flags;
>> + if (ht_capa)
>> + memcpy(&req.ht_capa, ht_capa, sizeof(req.ht_capa));
>> + if (ht_capa_mask)
>> + memcpy(&req.ht_capa_mask, ht_capa_mask,
>> + sizeof(req.ht_capa_mask));
>
> I think somewhere here you should mask this mask with the
> ht_capa_mod_mask. That way, you force drivers to advertise a correct
> ht_capa_mod_mask, if you don't do that we will certainly see drivers use
> more of ht_capa than contained in ht_capa_mod_mask. Probably should be a
> helper function since I think you might need it in more places.
Sure, I can add that.
Thanks,
Ben
>
> johannes
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-11-07 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 20:10 [PATCH v4 1/2] wireless: Support ht-capabilities over-rides greearb
2011-11-04 20:10 ` [PATCH v4 2/2] mac80211: Support ht-cap over-rides greearb
2011-11-07 9:13 ` Johannes Berg
2011-11-07 16:19 ` Ben Greear
2011-11-07 17:06 ` Johannes Berg
2011-11-04 21:03 ` [PATCH v4 1/2] wireless: Support ht-capabilities over-rides Johannes Berg
2011-11-07 9:06 ` Johannes Berg
2011-11-07 16:27 ` Ben Greear [this message]
2011-11-07 17:02 ` Johannes Berg
2011-11-07 17:40 ` Ben Greear
2011-11-07 17:42 ` Johannes Berg
2011-11-07 17:45 ` Ben Greear
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=4EB806D7.6050104@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).