From: Johannes Berg <johannes@sipsolutions.net>
To: Alexander Wetzel <alexander@wetzel-home.de>,
Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/4] iwlwifi: Enable Extended Key ID for mvm and dvm
Date: Tue, 20 Aug 2019 09:13:46 +0200 [thread overview]
Message-ID: <b2a2abf85761a3101afd11ff513d5fef62c6cd64.camel@sipsolutions.net> (raw)
In-Reply-To: <42653433-58b5-10f0-288e-1e5731e012d1@wetzel-home.de>
Hi,
> You are thinking about keeping the tx API untouched and modify the key
> install logic?
> Just prevent the firmware to activate a key for Tx when it's installed
> and notify the firmware by some means when the key can be used for Tx
> and then switch everything to the new key?
Something like that, yes.
> I guess there is no practical way I can get access to the firmware code,
> correct?
There isn't, yeah.
> For me it sounds harder than the optional flag extension I had
> in mind for the new tx API.
Much more of the TX path is actually wired into the hardware, rather
than being software. I'm not sure how much of this (key selection)
really is though.
> So let's wait and see what you can turn up. Till then we have more than
> enough other cards supporting Extended Key ID:-)
Yeah. I'll take a look, but I can't promise right now to work on it high
priority.
johannes
prev parent reply other threads:[~2019-08-20 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 19:50 [PATCH 1/4] mac80211_hwsim: Extended Key ID API update Alexander Wetzel
2019-06-29 19:50 ` [PATCH 2/4] mac80211: Simplify Extended Key ID API Alexander Wetzel
2019-06-29 19:50 ` [PATCH 3/4] mac80211: AMPDU handling for rekeys with Extended Key ID Alexander Wetzel
2019-06-29 19:50 ` [PATCH 4/4] iwlwifi: Enable Extended Key ID for mvm and dvm Alexander Wetzel
2019-07-05 8:51 ` Luca Coelho
2019-08-17 8:31 ` Alexander Wetzel
2019-08-19 9:43 ` Johannes Berg
2019-08-19 15:52 ` Alexander Wetzel
2019-08-19 20:23 ` Johannes Berg
2019-08-19 21:15 ` Alexander Wetzel
2019-08-20 7:13 ` Johannes Berg [this message]
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=b2a2abf85761a3101afd11ff513d5fef62c6cd64.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexander@wetzel-home.de \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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).