From: Ben Greear <greearb@candelatech.com>
To: fengbin <arithdon@gmail.com>
Cc: Janusz Dziedzic <janusz.dziedzic@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Denis Kenzior <denkenz@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"hostap@lists.infradead.org" <hostap@lists.infradead.org>
Subject: Re: Question on setting key right after the EAPOL 4/4 is sent.
Date: Sat, 10 Jun 2017 09:01:30 -0700 [thread overview]
Message-ID: <593C17DA.7080603@candelatech.com> (raw)
In-Reply-To: <CADP2NhbXgHWo+BWhrKQndu5X7fzd2J9teqf-o6fSWwDMv8X5Hw@mail.gmail.com>
On 06/09/2017 04:51 PM, fengbin wrote:
> seems your firmware doesn't support HTT_DATA_TX_DESC_FLAGS0_NO_ENCRYPT?
> Otherwise , it should work perfectly because Key messages are marked as no hw encryption.
Well, it could be my bug.....but unless you have access to ath10k firmware, then
I can't explain further what is the particular issue. If you do have access,
then I can give you some hints to follow the code path in question.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2017-06-10 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 23:17 Question on setting key right after the EAPOL 4/4 is sent Ben Greear
2017-06-08 23:36 ` Denis Kenzior
2017-06-08 23:43 ` Ben Greear
2017-06-09 0:07 ` Denis Kenzior
2017-06-09 7:28 ` Johannes Berg
2017-06-09 13:10 ` Denis Kenzior
2017-06-09 19:56 ` Johannes Berg
2017-06-09 21:42 ` LINKMODE & OPERSTATE thoughts Denis Kenzior
2017-06-13 9:15 ` Johannes Berg
2017-06-09 13:46 ` Question on setting key right after the EAPOL 4/4 is sent Ben Greear
2017-06-09 20:01 ` Johannes Berg
2017-06-09 20:18 ` Ben Greear
2017-06-09 21:47 ` Janusz Dziedzic
2017-06-09 22:02 ` Ben Greear
[not found] ` <CADP2NhbXgHWo+BWhrKQndu5X7fzd2J9teqf-o6fSWwDMv8X5Hw@mail.gmail.com>
2017-06-10 16:01 ` Ben Greear [this message]
2017-06-10 19:13 ` Arend van Spriel
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=593C17DA.7080603@candelatech.com \
--to=greearb@candelatech.com \
--cc=arithdon@gmail.com \
--cc=denkenz@gmail.com \
--cc=hostap@lists.infradead.org \
--cc=janusz.dziedzic@gmail.com \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.