From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: brcmfmac interface combinations
Date: Fri, 21 Oct 2016 13:55:15 +0200 [thread overview]
Message-ID: <1477050915.4068.36.camel@sipsolutions.net> (raw)
Hi Arend,
I'm looking into the interface combinations stuff, mostly due to the
patches from QCA to add the support for differing beacon intervals.
One thing that I was considering, was to change the API
for cfg80211_check_combinations() to not require the driver to fill in
the # of interfaces of each given type, but just have it pass the new
one, if present, or so.
However, there's a major difference between brcmfmac and mac80211 (the
only "drivers" using this), namely this: mac80211 allows *adding* any
kind of interface, as long as you don't actually try to operate it.
brcmfmac, on the other hand, prevents even adding an interface if it
doesn't fit the combinations.
I'm wondering if this is intentional?
I suspect that we can't change mac80211 at this point, and the brcmfmac
behaviour might be unexpected to some people who are used to working
with mac80211, but I'm not sure you'd want to change it either?
johannes
reply other threads:[~2016-10-21 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1477050915.4068.36.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.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 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.