On 04/09/2012 05:59 PM, Vasanthakumar Thiagarajan wrote: > On Monday 09 April 2012 08:17 PM, Kalle Valo wrote: >> On 04/05/2012 07:56 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@xxxxxxxxxxxxxxxx> >>> Signed-off-by: Vasanthakumar Thiagarajan<vthiagar@xxxxxxxxxxxxxxxx> >> >> Otherwise looks good but there's a sparse warning: >> >> drivers/net/wireless/ath/ath6kl/cfg80211.c:2539:20: warning: incorrect >> type in assignment (different base types) >> drivers/net/wireless/ath/ath6kl/cfg80211.c:2539:20: expected unsigned >> short [unsigned] [short] [usertype]<noident> >> drivers/net/wireless/ath/ath6kl/cfg80211.c:2539:20: got restricted >> __le16 [usertype]<noident> > > grr, for some reason my sparse does not report this. How about the > change like the following over this patch so that we need not worry > about endianness in accessing rsn-cap?. Thanks!. Looks good to me. Kalle -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
