From: Marcel Holtmann <marcel@holtmann.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Matthew Wang <matthewmwang@google.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kirtika Ruchandani <kirtika@google.com>, Jouni Malinen <j@w1.fi>
Subject: Re: Flag for detecting 802.11r Fast BSS Transition support
Date: Wed, 21 Aug 2019 18:59:29 +0200 [thread overview]
Message-ID: <FB8ED8A5-6606-4818-9A44-8944C5DC0E96@holtmann.org> (raw)
In-Reply-To: <CA+ASDXPhX3Yet=dJn8Pet_inP1uyueFZqBmuNXvmTrjv1r497g@mail.gmail.com>
Hi Brian,
>> And if you have a distribution or an OEM that cares, then that is what is going to happen.
>
> I can see where you might not be particularly sympathetic to this
> concern, but where I re-started this thread, I added in Jouni, due to
> his mention of:
>
> "There are such drivers [supporting FT] especially in number of
> Android devices and I'd
> rather not break those use cases.." [1]
>
> That doesn't exactly sound like a case where he's willing to break
> compatibility with older kernels in new wpa_supplicant. But maybe I
> shouldn't put words in his mouth. (On the other hand, Android systems
> are likely to not ever get either kernel *or* wpa_supplicant version
> upgrades, so maybe it's not really a problem at all!)
>
> Anyway, I'll just cook a patch, and then figure out whether/how I can
> teach wpa_supplicant to respect it. (Or, continue forking
> wpa_supplicant as we have been wont to do...)
it would be beneficial for iwd and not just wpa_supplicant.
The try-and-error method is not really working for iwd since we are 100% event driven. It is important that we get told what is supported and what not before trying to connect or roam.
Regards
Marcel
next prev parent reply other threads:[~2019-08-21 16:59 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
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 [this message]
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=FB8ED8A5-6606-4818-9A44-8944C5DC0E96@holtmann.org \
--to=marcel@holtmann.org \
--cc=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).