From: Christian Lamparter <chunkeey@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] carl9170: advertise interface combinations
Date: Sat, 14 May 2011 01:39:34 +0200 [thread overview]
Message-ID: <201105140139.34401.chunkeey@googlemail.com> (raw)
In-Reply-To: <1305329300.32461.0.camel@jlt3.sipsolutions.net>
On Saturday 14 May 2011 01:28:20 Johannes Berg wrote:
> On Sat, 2011-05-14 at 00:35 +0200, Christian Lamparter wrote:
> > In order to provide multiple interfaces for a single device,
> > the driver is now required to advertise all possible
> > interface configurations to the stack.
>
> Cool, thanks! Note that currently it's not yet required, but
> whatever :-)
"currently" :D
"I want to make you aware that I plan to remove the
WIPHY_FLAG_ENFORCE_COMBINATIONS flag again soon, so that all
drivers that don't advertise valid combinations will not be able to have
multiple virtual interfaces."
> > with the standard firmware, iw now displays:
> > [...]
> > valid interface combinations:
> > * #{ IBSS, managed, AP, P2P-client, P2P-GO } <= 2,
> > total <= 2, #channels <= 1
>
> Since mac80211 doesn't allow multiple IBSS interfaces, I think you
> should leave that out. And I should probably make mac80211 complain if
> it's advertised erroneously.
what about "valid" configurations like:
1 IBSS + 1 AP [STA/P2P make less sense]?
(only one IBSS)
Regards,
Chr
next prev parent reply other threads:[~2011-05-13 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 22:35 [PATCH] carl9170: advertise interface combinations Christian Lamparter
2011-05-13 23:28 ` Johannes Berg
2011-05-13 23:39 ` Christian Lamparter [this message]
2011-05-13 23:48 ` Johannes Berg
2011-05-14 0:42 ` [PATCH v2] " Christian Lamparter
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=201105140139.34401.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).