From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
j@w1.fi
Subject: 60 GHz interface types (was: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210)
Date: Fri, 09 Nov 2012 09:39:06 +0100 [thread overview]
Message-ID: <1352450346.9238.9.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1351701417-3140-2-git-send-email-qca_vkondrat@qca.qualcomm.com>
On Wed, 2012-10-31 at 18:36 +0200, Vladimir Kondratiev wrote:
> Card wil6210 by Wilocity supports operation on the 60GHz band
>
> This development snapshot supports:
>
> - STA, PCP and monitor modes
Ok so I have a more fundamental question/comment/issue.
802.11ad obviously distinguishes between a regular BSS, IBSS, and the
new PBSS. We also differentiate between BSS and IBSS in our interface
types, so I have a feeling that maybe we should also differentiate here,
and not re-use the NL80211_IFTYPE_AP/... interface types.
It seems that then we'd also need a PBSS_P2P_CLIENT and PBSS_P2P_GO,
which is a bit odd, but then again we also do that for P2P_CLIENT vs.
normal managed and P2P_GO vs. AP.
I'm not sure if we're ever going to see chipsets that have 60GHz and
2.4/5 GHz combined, and are not going to just register two wiphy's with
the system for that, but if there was then this would certainly help
with interface combinations etc.
Even if there isn't, it could help tools like network-manager not manage
the 60 GHz device (without having to add special checks), which I
suspect is what you'd want? Not really sure though.
Thoughts?
johannes
next prev parent reply other threads:[~2012-11-09 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 16:36 [PATCH v5 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-10-31 16:36 ` [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-11-08 19:29 ` Luis R. Rodriguez
2012-11-11 16:15 ` Vladimir Kondratiev
2012-11-12 17:22 ` Kalle Valo
2012-11-12 17:58 ` Vladimir Kondratiev
2012-11-13 19:39 ` Johannes Berg
2012-11-09 8:39 ` Johannes Berg [this message]
2012-11-11 8:15 ` 60 GHz interface types (was: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210) Vladimir Kondratiev
2012-11-11 13:42 ` Johannes Berg
2012-11-11 16:53 ` Vladimir Kondratiev
2012-11-12 10:15 ` Johannes Berg
2012-11-12 10:24 ` Johannes Berg
2012-11-12 14:57 ` Vladimir Kondratiev
2012-11-12 15:17 ` Johannes Berg
2012-11-12 15:01 ` Vladimir Kondratiev
2012-11-12 17:22 ` Vladimir Kondratiev
2012-10-31 16:36 ` [PATCH v5 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev
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=1352450346.9238.9.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@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