From: Johannes Berg <johannes@sipsolutions.net>
To: Lior David <liord@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
Jouni Malinen <jouni@qca.qualcomm.com>,
Dedy Lansky <dlansky@codeaurora.org>,
Maya Erez <merez@codeaurora.org>,
Hamad Kadmany <qca_hkadmany@qca.qualcomm.com>
Subject: Re: [PATCH] cfg80211: basic support for PBSS network type
Date: Tue, 26 Jan 2016 12:22:26 +0100 [thread overview]
Message-ID: <1453807346.2759.29.camel@sipsolutions.net> (raw)
In-Reply-To: <56961335.4040801@codeaurora.org>
On Wed, 2016-01-13 at 11:04 +0200, Lior David wrote:
>
> + * @NL80211_ATTR_PBSS: flag attribute. If set it means operate
> + * in a PBSS. Specified in %NL80211_CMD_CONNECT to request
> + * connecting to a PCP, and in %NL80211_CMD_START_AP to start
> + * a PCP instead of AP. Relevant for DMG networks only.
I'm continually confused by this; is it possible for DMG devices to be
a "real" AP rather than a PCP?
> @@ -3461,6 +3462,8 @@ static int nl80211_start_ap(struct sk_buff *skb, struct genl_info *info)
> return PTR_ERR(params.acl);
> }
>
> + params.pbss = nla_get_flag(info->attrs[NL80211_ATTR_PBSS]);
> +
> wdev_lock(wdev);
> err = rdev_start_ap(rdev, dev, ¶ms);
> if (!err) {
This, and the corresponding code in nl80211_connect, really ought to
check that the device is a DMG device and able to do this.
Perhaps this even needs a capability check, or do we assume that all
devices/drivers will be able to do this (or should reject it?)
If you want to rely on drivers though you need to have (in this patch!)
a small change to the existing driver to reject the operations if
pbss==true since obviously it cannot be doing the right thing right now
without further changes. That reject would then of course be removed
again with the driver update.
johannes
next prev parent reply other threads:[~2016-01-26 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 9:04 [PATCH] cfg80211: basic support for PBSS network type Lior David
2016-01-26 11:22 ` Johannes Berg [this message]
2016-01-26 12:34 ` Lior David
2016-01-26 12:54 ` Johannes Berg
2016-01-28 8:58 ` [PATCH v2] " Lior David
2016-02-02 15:09 ` Johannes Berg
2016-02-02 15:10 ` Johannes Berg
2016-02-03 9:24 ` Lior David
2016-02-03 15:39 ` Johannes Berg
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=1453807346.2759.29.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dlansky@codeaurora.org \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=liord@codeaurora.org \
--cc=merez@codeaurora.org \
--cc=qca_hkadmany@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).