From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>,
Subramania Sharma <sharmat@qca.qualcomm.com>
Subject: Re: [PATCH V2] ath6kl: Fix 4-way handshake failure in AP and P2P GO mode
Date: Mon, 9 Apr 2012 18:34:14 +0300 [thread overview]
Message-ID: <4F830176.1060604@qca.qualcomm.com> (raw)
In-Reply-To: <1333984880-4328-1-git-send-email-vthiagar@qca.qualcomm.com>
On 04/09/2012 06:21 PM, Vasanthakumar Thiagarajan wrote:
> RSN capability field of RSN IE which is generated (which is what really
> advertised in beacon/probe response) differs from the one generated in
> wpa_supplicant. This inconsistency in rsn IE results in 4-way handshake
> failure. To fix this, configure rsn capability used in wpa_supplicant
> in firmware using a new wmi command, WMI_SET_IE_CMDID. There is a bit
> (ATH6KL_FW_CAPABILITY_RSN_CAP_OVERRIDE) in fw_capabilities to advertise
> this support to driver.
>
> Signed-off-by: Subramania Sharma <sharmat@qca.qualcomm.com>
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Thanks, applied. But there were conflicts, please check that I didn't
break anything.
Kalle
next prev parent reply other threads:[~2012-04-09 15:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <\>
2011-05-19 1:24 ` [PATCH] Remove unused PROC_CHANGE_PENALTY constant Stephen Boyd
2011-07-15 5:26 ` [PATCH 0/1] linux-yocto/meta: update SRCREVs Bruce Ashfield
2011-07-15 5:26 ` [PATCH 1/1] linux-yocto/meta-yocto: update SRCREVS Bruce Ashfield
2011-07-20 14:51 ` Richard Purdie
2012-04-09 15:21 ` [PATCH V2] ath6kl: Fix 4-way handshake failure in AP and P2P GO mode Vasanthakumar Thiagarajan
2012-04-09 15:34 ` Kalle Valo [this message]
2012-04-09 16:00 ` Joe Perches
2012-04-10 7:50 ` Vasanthakumar Thiagarajan
2014-02-12 7:10 ` [PATCH v2] can: xilinx CAN controller support Kedareswara rao Appana
2014-02-12 7:10 ` Kedareswara rao Appana
2014-02-12 7:10 ` Kedareswara rao Appana
2014-02-13 19:20 ` Marc Kleine-Budde
2014-02-13 19:20 ` Marc Kleine-Budde
2014-02-14 8:55 ` Michal Simek
2014-02-14 8:55 ` Michal Simek
2014-02-14 9:04 ` Marc Kleine-Budde
2014-02-14 9:04 ` Marc Kleine-Budde
2014-02-14 9:13 ` Michal Simek
2014-02-14 9:13 ` Michal Simek
2014-02-14 9:16 ` Marc Kleine-Budde
2014-02-14 9:16 ` Marc Kleine-Budde
[not found] ` <52FD1B16.6020600-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-02-14 9:36 ` Appana Durga Kedareswara Rao
2014-02-14 9:36 ` Appana Durga Kedareswara Rao
2014-02-14 9:36 ` Appana Durga Kedareswara Rao
2014-02-14 9:59 ` Marc Kleine-Budde
2014-02-14 9:59 ` Marc Kleine-Budde
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=4F830176.1060604@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sharmat@qca.qualcomm.com \
--cc=vthiagar@qca.qualcomm.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 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.