On Wednesday 30 November 2011 12:17 PM, Kalle Valo wrote:
> Mohammed Shafi Shajakhan 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
Mohammed Shafi Shajakhan 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 seem
> to be beacons a
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 fo
On 30 November 2011 10:35, Peter Stuge wrote:
> Adrian Chadd wrote:
>> * wait for the TX DMA to complete (and hope it does, rather than get stuck);
>
> Under what circumstances does DMA typically get stuck in your
> experience?
On FreeBSD? I only get that when doing channel scans. I haven't
figur
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
ht
Adrian Chadd wrote:
> * wait for the TX DMA to complete (and hope it does, rather than get stuck);
Under what circumstances does DMA typically get stuck in your
experience?
//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.
From: Mohammed Shafi Shajakhan
change the AR_DEF_ANTENNA register settings i.e setting default antenna
setting only for antenna diversity enabled chipsets. no point in
doing this for MIMO chipsets
Signed-off-by: Mohammed Shafi Shajakhan
---
drivers/net/wireless/ath/ath9k/recv.c | 23
From: Mohammed Shafi Shajakhan
GPIO pin 4 is assigned AR9462 chipsets LED.
while GPIO pin 0 worked for obselete AR9462 chipsets though
they are meant for EEPROM as per Russell
Cc: Senthil Balasubramanian
Signed-off-by: Russell Hu
Signed-off-by: Mohammed Shafi Shajakhan
---
drivers/net/wirele
From: Mohammed Shafi Shajakhan
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
---
drivers/net/wireless/ath/ath9k/recv.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/n
.. hm. If edma is true, then you're using an AR9300 or later series
NIC. I have no idea (yet) about how the EDMA stuff works for the
AR9300 and later MAC/PCU.
Sorry. :)
MPDUs aren't delivered to the hardware at transmission time. They're
delivered before the transmission time. Otherwise throughpu
Hi all,
I have some question related to defined value. In ieee80211.h there is
#define IEEE80211_QOS_CTL_ACK_POLICY_NORMAL 0x
#define IEEE80211_QOS_CTL_ACK_POLICY_NOACK 0x0020
#define IEEE80211_QOS_CTL_ACK_POLICY_NO_EXPL0x0040
#define IEEE80211_QOS_CTL_ACK_POLICY_BLOCKACK 0x0
Thank you a lot for your answer.
I am aware about the A-MPDU size constraint. Data exceeding the announced size
will be considered as noise. This is not a problem!
I do not use RTS/CTS
I will disable the use of the Block ack. I do not need any feedback policy!
When I saw your example :
http
Hi,
I have been trying to get my ar9390 based wlan module to work as an AP
on my powerpc target. There seems to be some issues with AGC
calibration though. As soon as I start hostapd, I get the following:
ath9k :01:00.0: mon.wlan0: Features changed: 0x4800 -> 0x4000
ath: Unable to res
13 matches
Mail list logo
