Searched hist:"1052261 e4bba9879c1d7d519c8e8606c5d4264d5" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/drivers/net/wireless/ath/ath6kl/ |
H A D | core.h | diff 1052261e4bba9879c1d7d519c8e8606c5d4264d5 Thu Oct 27 08:00:13 CDT 2011 Jouni Malinen <jouni@qca.qualcomm.com> ath6kl: Report unique remain-on-channel cookie values
Even though only a single concurrent remain-on-channel operation is supported, there may be two pending remain-on-channel events (one to indicate end of a canceled operation and another to indicate start of a new operation). User space won't be able to distinguish these events unless unique cookies are used.
The previous behavior resulted in wpa_supplicant getting quite confused about the driver's offchannel state in various sequences and this made the P2P state machine behave incorrectly. Use of more than a single remain-on-channel cookie value fixes this.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
H A D | wmi.c | diff 1052261e4bba9879c1d7d519c8e8606c5d4264d5 Thu Oct 27 08:00:13 CDT 2011 Jouni Malinen <jouni@qca.qualcomm.com> ath6kl: Report unique remain-on-channel cookie values
Even though only a single concurrent remain-on-channel operation is supported, there may be two pending remain-on-channel events (one to indicate end of a canceled operation and another to indicate start of a new operation). User space won't be able to distinguish these events unless unique cookies are used.
The previous behavior resulted in wpa_supplicant getting quite confused about the driver's offchannel state in various sequences and this made the P2P state machine behave incorrectly. Use of more than a single remain-on-channel cookie value fixes this.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
H A D | cfg80211.c | diff 1052261e4bba9879c1d7d519c8e8606c5d4264d5 Thu Oct 27 08:00:13 CDT 2011 Jouni Malinen <jouni@qca.qualcomm.com> ath6kl: Report unique remain-on-channel cookie values
Even though only a single concurrent remain-on-channel operation is supported, there may be two pending remain-on-channel events (one to indicate end of a canceled operation and another to indicate start of a new operation). User space won't be able to distinguish these events unless unique cookies are used.
The previous behavior resulted in wpa_supplicant getting quite confused about the driver's offchannel state in various sequences and this made the P2P state machine behave incorrectly. Use of more than a single remain-on-channel cookie value fixes this.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|