From: Christian Lamparter <chunkeey@googlemail.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: "Yeoh Chun-Yeow" <yeohchunyeow@gmail.com>,
Kalle Valo <kvalo@adurom.com>, Adrian Chadd <adrian@freebsd.org>,
Jouni Malinen <j@w1.fi>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, jirislaby@gmail.com,
mcgrof@qca.qualcomm.com, ath5k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath5k: add support of HW encryption in management frames
Date: Tue, 11 Sep 2012 19:31:23 +0200 [thread overview]
Message-ID: <201209111931.24258.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAFtRNNwXgr=oN8y9u9MnEt75dAL0R-tJ6yf6vTOMcnCuCb7S-A@mail.gmail.com>
On Tuesday 11 September 2012 18:36:27 Nick Kossifidis wrote:
> 2012/9/11 Yeoh Chun-Yeow <yeohchunyeow@gmail.com>:
> >> To be more clear: you can tell the hw to *only* disable decryption and
> >> keep doing encryption.
> >
> > But the question here is that during Rx, need to do SW decryption for
> > management frame and then HW decryption for unicast data frame for all
> > the frame coming from the same STA. I still not so sure how to do
> > that.
> >
> > Jouni said that the workaround is to re-encrypt(incorrectly) received
> > robust unicast management frames if hwaccel for CCMP was configured
> > for the transmitting STA (this is to undo the incorrect decryption
> > done by the hardware) and then pass the encrypted frame to mac80211
> > for software decryption.
> >
>
> How about disabling acks on hw completely and handle them on sw ?
> This might keep the engine running ok for unicast frames.
>
> #define AR5K_DIAG_SW_DIS_ACK 0x00000002 /* Disable ACKs */
> #define AR5K_DIAG_SW_DIS_CTS 0x00000004 /* Disable CTSs */
No, CTS and ACKs are control frames and not management frames.
next prev parent reply other threads:[~2012-09-11 17:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 9:34 [PATCH] ath5k: add support of HW encryption in management frames Chun-Yeow Yeoh
2012-08-31 6:58 ` Adrian Chadd
2012-08-31 15:24 ` Yeoh Chun-Yeow
2012-09-03 19:24 ` Adrian Chadd
2012-09-04 1:03 ` Yeoh Chun-Yeow
2012-09-04 8:11 ` Johannes Berg
2012-09-04 9:28 ` Yeoh Chun-Yeow
2012-09-04 9:31 ` Johannes Berg
2012-09-04 10:22 ` Jouni Malinen
2012-09-04 11:21 ` Yeoh Chun-Yeow
2012-09-04 11:25 ` Yeoh Chun-Yeow
2012-09-04 11:35 ` Johannes Berg
2012-09-04 16:41 ` Yeoh Chun-Yeow
2012-09-04 16:54 ` Johannes Berg
2012-09-05 6:52 ` Yeoh Chun-Yeow
2012-09-04 16:55 ` Christian Lamparter
2012-09-04 16:57 ` Johannes Berg
2012-09-05 7:16 ` Jouni Malinen
2012-09-05 7:31 ` Yeoh Chun-Yeow
2012-09-05 8:03 ` Jouni Malinen
2012-09-07 3:51 ` Yeoh Chun-Yeow
2012-09-09 1:47 ` Adrian Chadd
2012-09-10 13:13 ` Kalle Valo
2012-09-10 15:11 ` Yeoh Chun-Yeow
2012-09-11 6:46 ` Nick Kossifidis
2012-09-11 9:42 ` Yeoh Chun-Yeow
2012-09-11 15:05 ` Nick Kossifidis
2012-09-11 15:51 ` Yeoh Chun-Yeow
2012-09-11 16:06 ` Nick Kossifidis
2012-09-11 16:07 ` Nick Kossifidis
2012-09-11 16:20 ` Yeoh Chun-Yeow
2012-09-11 16:30 ` Adrian Chadd
2012-09-11 16:36 ` Nick Kossifidis
2012-09-11 16:39 ` Johannes Berg
2012-09-11 17:31 ` Christian Lamparter [this message]
2012-09-11 17:48 ` Nick Kossifidis
2012-09-05 7:11 ` Jouni Malinen
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=201209111931.24258.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=adrian@freebsd.org \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=j@w1.fi \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=mickflemm@gmail.com \
--cc=yeohchunyeow@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).