From: Antonio Quartulli <antonio@meshcoding.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k pending patches
Date: Wed, 27 Nov 2013 13:52:45 +0100 [thread overview]
Message-ID: <5295EB1D.1050604@meshcoding.com> (raw)
In-Reply-To: <21141.51790.303263.385517@gargle.gargle.HOWL>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Sujith,
On 27/11/13 11:32, Sujith Manoharan wrote:
>> * In both chips, "mac_postamble" needs an update - the
>> "ALWAYS_PERFORM_KEY_SEARCH" bit has to enabled. This is required
>> to address key cache corruption, which needs a bigger change in
>> the driver.
What patch is addressing this change? And can could please explain a
bit more about what is needed to address the key cache corruption problem?
Right now I am working on a "reactive behavior" which tries to detect
a cache corruption event and subsequently re-install all the keys one
by one to ensure they are back to a proper state.
What does this ALWAYS_PERFORM_KEY_SEARCH bit do? Is it set within the
initvalues?
Sorry for shooting all these questions at once, but I am really trying
to understand how to properly address this issue.
Cheers,
- --
Antonio Quartulli
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBCAAGBQJSlesdAAoJEADl0hg6qKeOwmYQALqHy2dYH77rgEUU6aXw9ulA
CKug0IeFESSoThkBeBtjKyH3xaLmH/d9AiInQWhawpSUblWu3d5+p37f1pdcuS/t
6M8rPbbW+1E/ig/tiYCWneyqJA7p/F5IQ/h0v/ScLwQaE+h2Dszdt+erIF8MgM19
TQuIJOR9HoMnw3d2I7Z6gCXxDY7lmuKjOH+5RJUq8xpJellgbRjvYk7hy0Y5TGYr
F0t3v3iA41VyFozVIGIXPM4O0+LAnK9iz6kEJ/PDdSOFxqxRPnhFtTPkyBKYCj6I
druE5L9NbzofKjEQEbU15Pr/8uHfCXo+INUbWVdvFtpjjRRGsrDzCnYTtIWd2XOL
AaV0hYIoSbs8Pbp03iOM4BKFj+dJXw6bfKWQZ5aB6jiEJqI7YCEzQKUgShz+bHR3
HYv9mP9y6BSku/kJUk3SZGx/3NtzqsYYwkMHaf8Z7Z9HVwLbc6WYVMcvgVuxs4Ke
L1gsnWadrctkyFQXeneVXbWyGVAsG/KbcMaR90mrac27Dw11JtdG+BdUjz56G7H4
WByXuCmzd4X57Mq5uKmiVXoZ+UpSDQ3psO5ZwdF2urJL0rODsp4CG41Oeziqmpu3
EViJkb9LG0seBKUsv9JLKwugl3WBT/E9dxNFwMSlJ+n3fBShbMQeZV8Ba1JwtFo9
W10ywtInm4RYf5UK8VUW
=4CbN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-11-27 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:23 [PATCH 0/2] ath9k initval updates Sujith Manoharan
2013-11-27 10:23 ` [PATCH 1/2] ath9k: Update initvals for AR9300 v2.2 Sujith Manoharan
2013-11-27 10:23 ` [PATCH 2/2] ath9k: Update initvals for AR9580 v1.0 Sujith Manoharan
2013-11-27 10:32 ` ath9k pending patches Sujith Manoharan
2013-11-27 12:31 ` Antonio Quartulli
2013-11-27 15:20 ` Sujith Manoharan
2013-11-27 15:42 ` Antonio Quartulli
2013-11-27 12:52 ` Antonio Quartulli [this message]
2013-11-27 15:33 ` Sujith Manoharan
2013-11-27 15:43 ` Antonio Quartulli
2013-11-27 15:58 ` Antonio Quartulli
2013-11-27 16:00 ` Felix Fietkau
2013-11-27 16:34 ` Sujith Manoharan
-- strict thread matches above, loose matches on Subject: below --
2013-09-16 6:04 Sujith Manoharan
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=5295EB1D.1050604@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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.