From: Johannes Berg <johannes@sipsolutions.net>
To: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] cfg80211: Fix incompatible interfaces combination
Date: Tue, 05 Jun 2012 11:33:24 +0200 [thread overview]
Message-ID: <1338888804.4514.25.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FCDC838.9010209@qca.qualcomm.com>
Hi Mohammed,
> >> static const struct ieee80211_iface_limit a[] = {
> >> { .max = 2, .types = BIT(NL80211_IFTYPE_STATION) },
> >> };
> >>
> >> static const struct ieee80211_iface_limit b[] = {
> >> { .max = 2, .types = BIT(NL80211_IFTYPE_MESH_POINT) },
> >> };
> >>
> >> static const struct ieee80211_iface_combination if_comb[] = {
> >> {.limits = a,
> >> .n_limits = ARRAY_SIZE(a),
> >> .max_interfaces = 2,
> >> .num_different_channels = 1,
> >> },
> >> {.limits = b,
> >> .n_limits = ARRAY_SIZE(b),
> >> .max_interfaces = 2,
> >> .num_different_channels = 1,
> >> },
> >>
> >> };
> >>
> >> i could not add mesh interface if a managed interface is already there
> >> and vice versa. if this is the expected behavior, then fine.
> >
> > No, that's not expected! Another bug!
Actually, I'm sorry -- clearly I wasn't paying attention before -- it is
expected. The above means you can add two managed or two mesh interface,
but no combinations of them. Basically, the things in if_comb are XOR,
and the things inside each limit are AND.
johannes
next prev parent reply other threads:[~2012-06-05 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 15:47 [RFC] cfg80211: Fix incompatible interfaces combination Mohammed Shafi Shajakhan
2012-06-04 15:52 ` Johannes Berg
2012-06-04 15:59 ` Mohammed Shafi Shajakhan
2012-06-04 16:13 ` Johannes Berg
2012-06-04 16:16 ` Mohammed Shafi Shajakhan
2012-06-04 16:18 ` Johannes Berg
2012-06-04 16:19 ` Johannes Berg
2012-06-05 6:36 ` Mohammed Shafi Shajakhan
2012-06-05 6:48 ` Johannes Berg
2012-06-05 8:50 ` Mohammed Shafi Shajakhan
2012-06-05 9:33 ` Johannes Berg [this message]
2012-06-05 9:54 ` Mohammed Shafi Shajakhan
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=1338888804.4514.25.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mohammed@qca.qualcomm.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).