From: Brian Norris <briannorris@chromium.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Matthew Wang <matthewmwang@google.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kirtika Ruchandani <kirtika@google.com>,
j@w1.fi
Subject: Re: Flag for detecting 802.11r Fast BSS Transition support
Date: Thu, 8 Aug 2019 10:15:32 -0700 [thread overview]
Message-ID: <CA+ASDXOyXb0dPGOrjQR7C-b6dyftiZhkta3cwG28B9sC5wxHxQ@mail.gmail.com> (raw)
In-Reply-To: <211816ff03cf188d834a21b1fbc98b4f8c5b81f4.camel@sipsolutions.net>
+ Jouni
I forgot this was dangling:
On Mon, Apr 8, 2019 at 12:52 PM Johannes Berg <johannes@sipsolutions.net> wrote:
> So I guess you'd have to figure out what operations the drivers need to
> support then? I'm not even sure how wpa_s would handle this for SME
> offload devices.
I'm not intimately familiar with FT, but it looks like the only thing
wpa_supplicant is asking for is NL80211_CMD_UPDATE_FT_IES. I see
exactly one driver that implements this, but there's no flag for it.
Well, I guess we could just run the command and look for EOPNOTSUPP...
Jouni also claims [1] that there are plenty of out-of-tree non-SME
drivers that support FT. Android drivers may not be directly relevant
to upstream, but this topic does affect our ability to use
wpa_supplicant generically.
Brian
[1] http://lists.infradead.org/pipermail/hostap/2019-April/039951.html
next prev parent reply other threads:[~2019-08-08 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 19:06 Flag for detecting 802.11r Fast BSS Transition support Matthew Wang
2019-04-03 21:02 ` Brian Norris
2019-04-08 19:52 ` Johannes Berg
2019-08-08 17:15 ` Brian Norris [this message]
2019-08-16 18:54 ` Marcel Holtmann
2019-08-16 20:29 ` Brian Norris
2019-08-17 13:40 ` Marcel Holtmann
2019-08-21 16:54 ` Brian Norris
2019-08-21 16:59 ` Marcel Holtmann
2019-08-21 8:03 ` 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=CA+ASDXOyXb0dPGOrjQR7C-b6dyftiZhkta3cwG28B9sC5wxHxQ@mail.gmail.com \
--to=briannorris@chromium.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kirtika@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=matthewmwang@google.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).