From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [RFC] cfg80211: Fix incompatible interfaces combination
Date: Mon, 4 Jun 2012 21:46:56 +0530 [thread overview]
Message-ID: <4FCCDF78.4040606@qca.qualcomm.com> (raw)
In-Reply-To: <1338826398.4512.23.camel@jlt3.sipsolutions.net>
On Monday 04 June 2012 09:43 PM, Johannes Berg wrote:
> On Mon, 2012-06-04 at 21:29 +0530, Mohammed Shafi Shajakhan wrote:
>> On Monday 04 June 2012 09:22 PM, Johannes Berg wrote:
>>> On Mon, 2012-06-04 at 21:17 +0530, Mohammed Shafi Shajakhan wrote:
>>>> From: Mohammed Shafi Shajakhan<mohammed@qca.qualcomm.com>
>>>>
>>>> *if any interface type is not advertised by the driver
>>>> via ieee80211_iface_combination make sure we will have it
>>>> as a single interface only. lets that we will not add
>>>> an incompatible interface if some other interface is
>>>> already present. we cannot add any other interface,
>>>> if the already present interface is an incompatible
>>>> interface. for example in ath9k we don't advertise ADHOC in
>>>> ieee80211_iface_combination structure in the driver,
>>>> so it can only exist as an single interface
>>>
>>> I'm not sure I understand what you're changing here?
>>
>> if an interface say ad-hoc is not advertised in iface combination,
>> with the current still we can add that interface with some other
>> interface(removing the driver checks).
>>
>> in ath9k we have
>>
>> static const struct ieee80211_iface_limit if_limits[] = {
>> { .max = 2048, .types = BIT(NL80211_IFTYPE_STATION) |
>> BIT(NL80211_IFTYPE_P2P_CLIENT) |
>> BIT(NL80211_IFTYPE_WDS) },
>> { .max = 8, .types =
>> #ifdef CONFIG_MAC80211_MESH
>> BIT(NL80211_IFTYPE_MESH_POINT) |
>> #endif
>> BIT(NL80211_IFTYPE_AP) |
>> BIT(NL80211_IFTYPE_P2P_GO) },
>> };
>>
>> i am able to create an IBSS interface even if a STA interface is up and
>> running in ath9k(removing the driver checks).
>>
>> this patch ensures that if we have an incompatible interface, it is the
>> only one can that can exist.
>
> Right, ok, I see that it's broken now, trying to see if there's a better
> fix though.
sure, thank you.
>
> johannes
>
--
thanks,
shafi
next prev parent reply other threads:[~2012-06-04 16:17 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 [this message]
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
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=4FCCDF78.4040606@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.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 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.