From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs.
Date: Thu, 4 Feb 2016 09:52:17 -0800 [thread overview]
Message-ID: <56B38FD1.40902@candelatech.com> (raw)
In-Reply-To: <1454576521.2564.6.camel@sipsolutions.net>
On 02/04/2016 01:02 AM, Johannes Berg wrote:
> On Tue, 2016-01-26 at 07:19 -0800, Ben Greear wrote:
>
>> As far as I can tell, that will not work, because I want to have
>> multiple station devices per radio, and have each of them be able to
>> use a different configuration. So, one station may be /g, and
>> another /n and another /AC. Same with APs. In addition, some
>> stations may want to use all available rates for their mode, and
>> others may want to use a fixed rate or subset of available rates.
>
> So let's agree that we're splitting the *used* rates (which we have
> today) and the *advertised* rates/modes/...
Yes, I think that will work well, and unless I mis-understand, that
is basically what I implemented so far.
> Even if we can't modify the wiphy capabilities, perhaps we could still
> handle it more consistently at mac80211 level, e.g. by introducing and
> using "sdata->capa.bands" (and similar for all the other wiphy
> capabilities you want to manipulate), and then allowing that to point
> to something modified?
Copied state might be tricky. I think if we hold any copies of capabilities data in
the sdata, then it should be logically compared with a mask and then treated as an AND with whatever the wiphy
has. I'm reluctant to propose any serious mac80211 change at this point, though perhaps
as more of this type of features are added, then it will become more obvious how
to nicely consolidate things in mac80211.
To be honest, I thought my -v2 patches were fairly non-invasive compared to my
normal hackings :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-02-04 17:52 UTC|newest]
Thread overview: 26+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2015-10-20 17:22 greearb
2015-10-20 17:26 ` 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=56B38FD1.40902@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.