From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
before concluding that the recieved beacon is for us, let us make sure
that the BSSID is non-zero.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/recv.c |1 +
1 files changed, 1
Mohammed Shafi Shajakhan wrote:
before concluding that the recieved beacon is for us, let us make sure
that the BSSID is non-zero.
Under what circumstances would the BSSID be zero?
//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
Hi Peter,
On Wednesday 30 November 2011 08:06 AM, Peter Stuge wrote:
Mohammed Shafi Shajakhan wrote:
before concluding that the recieved beacon is for us, let us make sure
that the BSSID is non-zero.
Under what circumstances would the BSSID be zero?
//Peter
unassociated state for
Mohammed Shafi Shajakhan moham...@qca.qualcomm.com writes:
unassociated state for station.
but I observed this when i tested ad-hoc mode. I just started an
ad-hoc mode creator and left it for some time with no one joining. i
observed there are few frames in rx_tasklet of ath9k driver which
On Wednesday 30 November 2011 12:17 PM, Kalle Valo wrote:
Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com writes:
unassociated state for station.
but I observed this when i tested ad-hoc mode. I just started an
ad-hoc mode creator and left it for some time with no one joining. i
observed
