From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs.
Date: Tue, 15 Mar 2016 15:15:49 +0100 [thread overview]
Message-ID: <1458051349.2871.19.camel@sipsolutions.net> (raw)
In-Reply-To: <56E1B556.4080004@candelatech.com>
On Thu, 2016-03-10 at 09:56 -0800, Ben Greear wrote:
> First, are you proposing that I make a copy of the entire local-
> >hw.wiphy->bands array and store it locally in sdata?
No, I think it should be pointers there, say
sdata->bands[X] pointing to the same thing as local->hw.wiphy->bands[X]
is pointing to.
So the first patch would introduce that, and replace each and every use
of local->hw.wiphy->bands[] with sdata->bands[], if necessary
annotating the remaining ones with why they're OK and should stay.
> And then, I would provide some API to modify the bands[i]->bitrates
> and other variables to properly select the advertised features?
Kinda. You'd provide some kind of helper function or API to take the
local->hw.wiphy->bands[X] and duplicate it into a newly allocated
buffer, modifying it along the way, before assigning it to the per-
sdata stuff in sdata->bands[X].
> I am a bit concerned about making copies (and then changing) the
> driver's bitrates array. Likely it will work with ath10k, but it
> seems fragile at best.
That's an interesting point, we currently use the rate *index* a lot,
so we have to find some way of preserving that. Perhaps we need to
introduce a flag indicating a given rate is disabled?
johannes
next prev parent reply other threads:[~2016-03-15 14:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 17:24 [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs greearb
2015-10-20 17:24 ` [PATCH-v2 2/2] mac80211: ensure association req uses configured ratemask greearb
2016-01-26 11:18 ` Johannes Berg
2015-11-05 18:47 ` [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs Ben Greear
2015-11-05 19:04 ` Johannes Berg
2016-01-26 11:16 ` Johannes Berg
2016-01-26 15:19 ` Ben Greear
2016-02-04 9:02 ` Johannes Berg
2016-02-04 17:52 ` Ben Greear
2016-02-18 20:32 ` Johannes Berg
2016-02-18 20:40 ` Ben Greear
2016-02-18 20:45 ` Johannes Berg
2016-02-18 20:59 ` Ben Greear
2016-02-18 21:14 ` Johannes Berg
2016-02-18 21:54 ` Ben Greear
2016-02-23 11:06 ` Johannes Berg
2016-03-10 17:56 ` Ben Greear
2016-03-15 14:15 ` Johannes Berg [this message]
2016-03-15 16:10 ` Ben Greear
2016-03-15 20:20 ` Johannes Berg
2016-06-10 18:43 ` Ben Greear
2016-06-21 9:40 ` Johannes Berg
2016-06-21 14:19 ` Ben Greear
2016-03-15 14:17 ` 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=1458051349.2871.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=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).