From: Jiri Slaby <jirislaby@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [PATCH 1/1] ath5k: 5211, don't crypt every protected frame
Date: Sun, 26 Apr 2009 12:37:41 +0200 [thread overview]
Message-ID: <49F43975.2060106@gmail.com> (raw)
In-Reply-To: <20090426020047.GA10885@hash.localnet>
On 04/26/2009 04:00 AM, Bob Copeland wrote:
> On Sat, Apr 25, 2009 at 02:09:23PM +0200, Jiri Slaby wrote:
>> Hi guys,
>> do you remember some 5211 HW which didn't work with this?
>> --
>>
>> Set null key type even on ar5211, otherwise it en/decrypts every frame with
>> protected bit set which renders the card unusable on encrypted networks.
>
> Not me. I don't have the hardware, so I would say if your patch is known
> to work on a 5211 then we go with it.
Ok, thanks. Of course the HW I used (IBM T40 Thinkpad) needs the patch ;).
next prev parent reply other threads:[~2009-04-26 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 12:09 [PATCH 1/1] ath5k: 5211, don't crypt every protected frame Jiri Slaby
2009-04-26 2:00 ` Bob Copeland
2009-04-26 10:37 ` Jiri Slaby [this message]
2009-04-26 14:13 ` Nick Kossifidis
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=49F43975.2060106@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.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).