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 v2] cfg80211: basic support for PBSS network type
Date: Tue, 02 Feb 2016 16:10:40 +0100 [thread overview]
Message-ID: <1454425840.2926.8.camel@sipsolutions.net> (raw)
In-Reply-To: <1454425741.2926.7.camel@sipsolutions.net> (sfid-20160202_160909_821108_CDA961D3)
On Tue, 2016-02-02 at 16:09 +0100, Johannes Berg wrote:
> On Thu, 2016-01-28 at 10:58 +0200, Lior David wrote:
> > PBSS (Personal Basic Service Set) is a new BSS type for DMG
> > networks. It is similar to infrastructure BSS, having an AP-like
> > entity called PCP (PBSS Control Point), but it has few differences.
> > PBSS support is mandatory for 11ad devices.
> >
> > Add support for PBSS by introducing a new PBSS flag attribute.
> > The PBSS flag is used in the START_AP command to request starting
> > a PCP instead of an AP, and in the CONNECT command to request
> > connecting to a PCP instead of an AP.
> >
> Applied.
>
Actually, one more question: Why does the kernel have to know at
*connect* time that it should be a PBSS? It could tell that from the
scan results, by looking for PBSS if it can't find AP in there, no?
johannes
next prev parent reply other threads:[~2016-02-02 15:10 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
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 [this message]
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=1454425840.2926.8.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).