linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: eliad@wizery.com
Subject: PSK/1x offload documentation ambiguity
Date: Thu, 18 Mar 2021 10:43:24 -0700	[thread overview]
Message-ID: <975404e3eebd91ccf17b172eb0969a5256c7fef3.camel@gmail.com> (raw)

Hi,

I see the API documentation for PSK/1x offload is somewhat ambiguous
with respect to if the hardware actually supports user space 4-way
handshakes. Both extended features say this regarding doing the 4-way
in the host:

"..., doing it in the host might not be supported"

So far the hardware I have used does support user space 4-way
handshakes so I have not yet bothered with offload. But this comment is
concerning if a user comes along with hardware that *does not* support
the 4-way in userspace. It would be nice to know if this comment is
complete bogus, or if there is actual hardware which does not support
user space 4-way handshakes. And if there is such hardware, how can
userspace know the difference.

I've CC'ed Eliad who is the author to 91b5ab6289 which added this
support.

Thanks,
James



                 reply	other threads:[~2021-03-18 17:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=975404e3eebd91ccf17b172eb0969a5256c7fef3.camel@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=eliad@wizery.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).