Signed-off-by: Sujith Manoharan [EMAIL PROTECTED]
---
drivers/net/wireless/ath9k/core.h | 275 +---
1 files changed, 130 insertions(+), 145 deletions(-)
diff --git a/drivers/net/wireless/ath9k/core.h
b/drivers/net/wireless/ath9k/core.h
index 903bd46..e294c1b
Signed-off-by: Sujith Manoharan [EMAIL PROTECTED]
---
drivers/net/wireless/ath9k/beacon.c |2 +-
drivers/net/wireless/ath9k/core.c | 73 +++
drivers/net/wireless/ath9k/core.h |3 +-
drivers/net/wireless/ath9k/recv.c |2 +-
drivers/net/wireless
Signed-off-by: Sujith Manoharan [EMAIL PROTECTED]
---
drivers/net/wireless/ath9k/core.c | 20 +---
drivers/net/wireless/ath9k/core.h |1 -
drivers/net/wireless/ath9k/rc.c |4 ++--
drivers/net/wireless/ath9k/xmit.c |2 +-
4 files changed, 12 insertions(+), 15
with that patch.
[1]: http://marc.info/?l=linux-wirelessm=122309915413328w=2
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
will be Welcome.
Did you compile wireless-testing ?
How are you trying to connect to the AP, using wpa_supplicant ?
If so, can you post the config ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo
development.
2. Is this driver has been shipped with some linux distributions?
Yep, any distribution that carries kernel 2.6.27 or above will carry ath9k.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo
out a patch that fixes this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
on
the first try, will the node buffer these frames and wait till it can
send the complete block up, or does it just forward up what it gets
after the block-ack is sent each time?
ieee80211_sta_manage_reorder_buf() in net/mac80211/rx.c contains
the answers you are looking for.
Sujith
. :)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
);
+
The queue is already available, we make sure of that before calling
ath_tx_start().
And the queue is sent through txctl.txq, you don't have to calculate the queue
number again.
So, just stopping the queue and moving the buffer back to the free list would
be enough.
Sujith
:9e:df:f6
wlan0: authentication with AP 00:11:95:9e:df:f6 timed out
A number of updates have gone into the wireless-testing tree.
You can use that tree or compat-wireless to get the latest driver
and check if the problem persists.
Sujith
___
ath9k-devel
could put it into main.c simply.
Your choice really, it doesn't matter much anyway. :)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Gabor Juhos wrote:
Convert to use bus-agnostic DMA routines to make it usable on AHB bus as well.
This pretty much makes the previous patch redundant.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman
gone into ath9k. Any kernel later than 2.6.27 would be a better
choice.
In that case you can use compat-wireless-2.6 to pull in the latest code.
See: http://wireless.kernel.org/en/users/Download
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel
load ath9k with debugging enabled, as 'modprobe ath9k debug=0x2000'
and post the output here.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
: CONFIG_ATH9K_DEBUG=y has to be present in your .config
Also, this option is present in newer kernels, so 2.6.29-rc2 should do fine.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org
.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
/Download
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
through iw
though. It seems this is due to the way our RC works... anyway this
could use some love too. Sujith may be working on this, not sure,
sujith?
In the end it would be nice to see minstrel be used anyway so a good
milestone is to allow ath9k select minstrel or let it use its own RC
The post at pastebin has expired...
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Enable CONFIG_ATH9K_DEBUG=y in config.mk, load ath9k with the module parameter
debug=0x2000, and then reproduce the issue and post the log here please. Thanks.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel
. However, I never saw any
rates 54 Mbps. Are the 11n rates available in ad-hoc mode? Thx a lot.
Nope, 11n hasn't been implemented for Ad-Hoc.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https
?
The chainmasks would automatically be 1x1 in legacy mode, see
ath9k_config()@main.c
and ath_update_chainmask().
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
find one.
2) Where I can get documentation for AR5*** and AR9*** chipsets? Does
it released for public access?
The code is the documentation. :)
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https
, give me a link to git tutorial. I want to modifi some wireless
files, but keep ability to update them by git pull... Sorry, I'm
newbie...
http://wireless.kernel.org/en/developers/Documentation/git-guide
Sujith
--
http://sujith-m.blogspot.com
___
ath9k
Steve Brown wrote:
For me, the ASSERT at rc.c:745 goes off.
I instrumented it. The results are attached.
Thanks for the trace. We'll work on this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman
On kernel 2.6.28.6 with compat-wireless 2009-02-19. All who have put
the AR9102 in client-mode seem to watch it quickly degrade to 0 or
1Mbps rate... which I do not see on a laptop with AR5418 MiniPCI card
using same compat-wireless.
Sujith or other developer tried ath9k on AP81 platform
current
channel width.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
, are you using ath9k as the AP ?
Can you paste the hostapd log ? (hostapd -dd)
From your other mail, the chosen rate table is completely wrong,
am not sure if this is related to AP mode in ath9k.
Sujith
___
ath9k-devel mailing list
ath9k-devel
Gabor Juhos wrote:
1. In some cases the ethernet interface goes down for a short time
after'ifconfig wlan0 up'.
2. Sometimes the device simply reboots itself after 'ifconfig wlan0 up'.
After I have added some printk statements into the code, I noticed that the
ar5416 and ar9100 devices use
Sujith Manoharan wrote:
I'll check the initval arrays and update.
Does this patch help ? I haven't tested on 9100, but 5416 works fine.
diff --git a/drivers/net/wireless/ath9k/hw.c b/drivers/net/wireless/ath9k/hw.c
index eb750a5..d7b3c44 100644
--- a/drivers/net/wireless/ath9k/hw.c
+++ b
to do a project with drivers that
support AMSDU and AMPDU packet aggregation. AFAK, ath9k (in the
wireless-testing
tree) supports this AMSDU and AMPDU packet aggregation. Is it true?
ath9k supports only AMPDU aggregation currently.
Sujith
___
ath9k
dereference. Will send out a patch fixing this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Gabor Juhos wrote:
According to Luis request, here is the new patch-set with detailed
explanations.
Series looks good, but it doesn't apply on current wireless-testing.
A rebase is needed ?
Sujith
___
ath9k-devel mailing list
ath9k-devel
;
}
IEEE80211_TX_CTL_RATE_CTRL_PROBE is to be used with fl...@ieee80211_tx_info
and is not a per-rate flag.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
in net-next-2.6 fixes a couple
of warnings (in eeprom.c).
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
supported by ath9k.
If that command doesn't work anymore, might someone please suggest me how
could I get the data out of the card's memory.
Take a look at eeprom.[ch] in ath9k/ and you could probably
write a parser or extend ath_info maybe ...
Sujith
remains
unclear, though.
We'll work on this issue.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
the driver with the modparam 'debug=0x200' and post the kernel
log when this issue happens ? Thanks.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
?
No. That flag is used to indicate whether we should
expect an ACK for the frame being sent.
The correct way would be to set AR_DIAG_ACK_DIS in AR_DIAG_SW (reg.h)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org
is at: http://linuxwireless.org/en/users/Download/
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
=0x600 and post the kernel log.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
://wireless.kernel.org/en/users/Drivers/ath9k/debug
That would show what exactly goes wrong when bringing up the interface.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
as the contents of RTC_RC is weird.
Which probably means that the earlier initialization messed up somewhere,
corrupting the RTC register space - this would be my immediate guess.
Will take a look. Thanks for the debug log.
Sujith
___
ath9k-devel
: [ 4432.123358] ath9k: NETWORK SLEEP - AWAKE
Disable power managament.
'iwconfig wlan0 power off'
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Benoit PAPILLAULT wrote:
I am seeing this as well on 2.6.33-rc4-wl, but only at unload time
(modprobe -r ath9k).
Yep, this happens because I changed the debug mask for that message to FATAL.
It is harmless, but can be fixed by cleaning up the virtual wiphy / idle stuff.
Sujith
Luis Rodriguez wrote:
Since the issues so far are obaserved on AR9160 and AR9220
(and not AR9280) and AR9271 (sujith) this might be a bus issue
and the only way to zero in on the issue would be by getting full
register dumps to ensure every other register related to ACK Timeout
is programmed
Dyno Fu wrote:
On Tue, Mar 30, 2010 at 11:47 AM, Sujith sujith.manoha...@atheros.com wrote:
Wiktor Zajas wrote:
Thanks so much for this driver, it's working flawlessly. Only one minor
problem was Michael MIC failure detected, changing to AES helped.
I don't know if what I've done
, because the firmware
does not report the actual transmission rate.
You can check the actual throughput using iperf.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
John W. Linville wrote:
Any feedback on this?
This has already been merged.
commit e92119ca88691ac2239916d31c3dcecd10867521
Author: Sujith sujith.manoha...@atheros.com
Date: Thu Apr 1 10:28:24 2010 +0530
ath9k_htc: Add TL-WN422G v2 product ID
Signed-off-by: Sujith sujith.manoha
=linux/kernel/git/mcgrof/ath9k_htc.git;a=snapshot;h=464e457b98dfd75223f50b3c9a11740b979135da;sf=tgz
Anybody give me a hand? Thanks!
ath9k_htc has been merged into wireless-testing.
See: http://wireless.kernel.org/en/users/Drivers/ath9k_htc
Sujith
;
- if (epid = ENDPOINT_MAX) {
+ if (epid = HST_ENDPOINT_MAX) {
if (pipe_id != USB_REG_IN_PIPE)
dev_kfree_skb_any(skb);
else
The original check was correct ...
Sujith
___
ath9k-devel
the htc_target struct should be changed to ENDPOINT_MAX?
Ah right. That should be fixed.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
called ath9k_htc. It's
present in the current wireless-testing branch and it's in process of
being propagated to other branches and stable kernels.
AR9287 is supported by ath9k, not ath9k_htc.
compat-wireless should support the chipset.
Sujith
___
ath9k
Dan Carpenter wrote:
After c11d8f89d3b7: ath9k_htc: Simplify TX URB management we no longer
assume that tx_buf is a non-null pointer.
Signed-off-by: Dan Carpenter erro...@gmail.com
Thanks.
Acked-by: Sujith sujith.manoha...@atheros.com
diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c
Dan Carpenter wrote:
This is obviously a small picky thing. The original error handling code
doesn't free the most recent allocations which haven't been added to the
hif_dev-tx.tx_buf list yet.
Signed-off-by: Dan Carpenter erro...@gmail.com
Thanks.
Acked-by: Sujith sujith.manoha
fine
But,
The bit rate is 1 MB/s and when I try to changed using
iwconfig wlan0 bitrate 54M
it says not supported
The reported TX rate is always 1 Mbps, because the firmware doesn't
report the actual tx rate.
Sujith
___
ath9k-devel
-off-by: Dan Carpenter erro...@gmail.com
Thanks.
Acked-by: Sujith sujith.manoha...@atheros.com
diff --git a/drivers/net/wireless/ath/ath9k/wmi.c
b/drivers/net/wireless/ath/ath9k/wmi.c
index e23172c..6260faa 100644
--- a/drivers/net/wireless/ath/ath9k/wmi.c
+++ b/drivers/net/wireless/ath
is currently working
on this, but it might change in the future. :)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
credits
You have the wrong firmware.
Please see http://wireless.kernel.org/en/users/Drivers/ath9k_htc.
I'll check the USB IDs and send a fix.
Thanks for reporting this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org
ATH9K_HTC_TX_RTSCTS and ATH9K_HTC_TX_CTSONLY
in ath9k_htc_tx_start() in htc_drv_txrx.c
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Natale Vinto wrote:
Hi,
I have a TP-LINK TL-WN722N USB dongle with AR9271 chipset, because I
would use it as AP i tried to use wireless-testing linville kernel
2.6.35-rc5 and tried to apply patches from Sujith that I found here:
http://marc.info/?t=12767669921r=1w=2
http://marc.info/?l
Pavel Machek wrote:
Hi!
Sujith, I see you fought with endianness issues on ath9k_htc
driver. Was you able to test it on actual hardware? Should I try the
version just after your commit?
No, I never had a chance to test the driver on a big-endian system.
I assume you are referring
Pavel Machek wrote:
...so I indentified two endianness problems in eeprom, but even with
both fixed, it still will not associate. Is there some way to dump USB
packets, then compare them between PC and PowerPC versions? Should I
expect them to match?
Does this patch help ?
diff --git
well.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
the firmware using
WMI_TXRATE_EVENTID in wmi.c
Also, check the 'tgt_stats' debugfs file to obtain retry statistics.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Tao Jin wrote:
Hi Sujith,
Thanks a lot for the reply! Is this fully supported in ath9k and ath5k?
Yep.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
a kernel novice. Are these names kinda standard naming
convention in driver development? or this has to do with the usb
chipset used in those wifi usb cards?
HTC is specific to the USB cards supported by ath9k_htc.
Sujith
___
ath9k-devel mailing list
Yevgeniy Melnichuk wrote:
hello Sujith,
same result, except the lines you mentioned are missing.
here is the exact output:
usb 1-1: new high speed USB device using ehci_hcd and address 15
usb 1-1: ath9k_htc: Transferred FW: ar7010_1_1.fw, size: 73028
usb 1-1: ath9k_htc: Target
the
value.
Otherwise, the config file used to compile the kernel would have the value.
I have a card with PID 0x7015 and it works fine here, so not sure where the
problem lies.
Can you post the output of uname -a, and /proc/cpuinfo ? Thanks.
Sujith
___
ath9k
device specifically for this knowing full well the
drivers weren't done yet :-)
There are a few issues with PS-buffering which requires modifications in the
firmware.
Hopefully, something will be posted soon.
Sujith
___
ath9k-devel mailing list
ath9k
tested rigorously, so consider this series as
experimental code.
Sujith
Sujith Manoharan (33):
ath9k_htc: Allow upto two simultaneous interfaces
ath9k_htc: Unify target capability updation
ath9k_htc: Fix error handling in add_interface
ath9k_htc: Remove OP_PREAMBLE_SHORT
ath9k_htc: Remove
From: Sujith Manoharan sujith.manoha...@atheros.com
Multiple interfaces can be configured if a slot is free
on the target. Monitor mode also requires a slot.
The maximum number of stations that can be handled in
the firmware is 8, manage the station slots accordingly.
Signed-off-by: Sujith
From: Sujith Manoharan sujith.manoha...@atheros.com
Update capabilites on the target once, when
start() is called, there is no need for redundant
updation on adding an interface.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc_drv_main.c
From: Sujith Manoharan sujith.manoha...@atheros.com
Addition of a station might fail - handle this error
properly by removing the VAP on the target.
Also, bail out immediately if the max. no of interfaces
has been reached.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers
From: Sujith Manoharan sujith.manoha...@atheros.com
mac80211's BSS info can be used for this.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h | 13 ++---
drivers/net/wireless/ath/ath9k/htc_drv_main.c |9 -
2
From: Sujith Manoharan sujith.manoha...@atheros.com
mac80211 stores the association state in ieee80211_bss_conf.
Use this and remove the local state, which is incorrect anyway
since it is stored globally and not on a per-VIF basis.
Restarting ANI and reconfiguration of HW beacon timers when
From: Sujith Manoharan sujith.manoha...@atheros.com
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h |5 +++
drivers/net/wireless/ath/ath9k/htc_drv_main.c | 35 +
2 files changed, 40 insertions(+), 0
From: Sujith Manoharan sujith.manoha...@atheros.com
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h|2 +-
drivers/net/wireless/ath/ath9k/htc_drv_beacon.c |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff
From: Sujith Manoharan sujith.manoha...@atheros.com
This is required when issuing commands to the firmware.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc_drv_main.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git
From: Sujith Manoharan sujith.manoha...@atheros.com
Match the beacon header with that of the firmware.
Also, the firmware reports the TSF for an SWBA, so
store it.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h |2 +-
drivers/net
From: Sujith Manoharan sujith.manoha...@atheros.com
This is required for allowing only one IBSS interface to be
configured.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h | 28 +
drivers/net/wireless/ath
From: Sujith Manoharan sujith.manoha...@atheros.com
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h |8
drivers/net/wireless/ath/ath9k/htc_drv_main.c | 11 +++
2 files changed, 19 insertions(+), 0 deletions
From: Sujith Manoharan sujith.manoha...@atheros.com
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc_drv_main.c | 15 ++-
1 files changed, 14 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_main.c
From: Sujith Manoharan sujith.manoha...@atheros.com
The time granularity for the ANI task is different for AP and
station mode.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h |1 +
drivers/net/wireless/ath/ath9k/htc_drv_main.c
From: Sujith Manoharan sujith.manoha...@atheros.com
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc_drv_main.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_main.c
b/drivers
From: Sujith Manoharan sujith.manoha...@atheros.com
Handle multi-interface situations by checking if
AP interfaces are already present.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h|3 +-
drivers/net/wireless/ath/ath9k
From: Sujith Manoharan sujith.manoha...@atheros.com
The target beacon transmission time has to be synced with the HW
TSF when configuring beacon timers in Adhoc mode. Failing to do this
would cause erroneous beacon transmission, for example, on completion
of a scan run to check for IBSS merges
From: Sujith Manoharan sujith.manoha...@atheros.com
In multi-interface mode, beacons/probe responses that are
sent out must have their timestamp field updated. Calculate
the TSF adjustment value for each beaconing interface and set it
in the frame properly.
Signed-off-by: Sujith Manoharan
From: Sujith Manoharan sujith.manoha...@atheros.com
Set operating parameters (cwmin, cwmax) for the beacon queue
in AP mode.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc_drv_beacon.c | 77 ++-
1 files changed, 46
From: Sujith Manoharan sujith.manoha...@atheros.com
Use the CAB endpoint to send buffered multicast or
broadcast frames after each SWBA event.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h|6 +++-
drivers/net/wireless/ath
From: Sujith Manoharan sujith.manoha...@atheros.com
Use a queue to handle WMI events and schedule a tasklet
to process the events. This fixes the race between the
WMI event ISR and the SWBA tasklet when the arrival of
WMI events in quick succession could overwrite the SWBA
data before the tasklet
From: Sujith Manoharan sujith.manoha...@atheros.com
The AID and BSSID should be set in the HW only for the
first station interface or adhoc interface. Also, cancel
the ANI timer in stop() for multi-STA scenario. And finally
configure the HW beacon timers only for the first station
interface
From: Sujith Manoharan sujith.manoha...@atheros.com
The length of the received SKB could be equal to
HTC_RX_FRAME_HEADER_SIZE in case of packets with phy/crc errors,
in which case they are dropped without being processed.
Fix this check so that the error counters are updated correctly.
Signed
From: Sujith Manoharan sujith.manoha...@atheros.com
There is no need to set the BSSID mask or opmode when
initializing RX, they would be set correctly in the HW reset
routine.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc_drv_txrx.c |8
From: Sujith Manoharan sujith.manoha...@atheros.com
WMI_TGT_TXQ_ENABLE_CMDID
WMI_HOST_ATTACH
WMI_DEBUG_INFO_CMDID
WMI_BEACON_UPDATE_CMDID
WMI_RESET_CMDID
WMI_RX_LINK_CMDID
WMI_ABORT_TXQ_CMDID
WMI_STOP_DMA_RECV_CMDID
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net
From: Sujith Manoharan sujith.manoha...@atheros.com
For all packets sent through the USB_WLAN_TX_PIPE endpoint,
the private area of the SKB's tx_info can be used to store
driver-specific information. For packets sent through USB_REG_OUT_PIPE,
this will not make a difference since they are routed
From: Sujith Manoharan sujith.manoha...@atheros.com
CTS protection can be obtained from mac80211 directly.
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/htc.h | 11 +--
drivers/net/wireless/ath/ath9k/htc_drv_main.c | 10
From: Sujith Manoharan sujith.manoha...@atheros.com
Transmission of beacons becomes erratic when TX load
is high, since the latency involved in the generation
of a SWBA interrupt on the target to the actual sending
of a beacon is quite high for USB devices.
Fix this by adjusting the beacon
From: Sujith Manoharan sujith.manoha...@atheros.com
Signed-off-by: Sujith Manoharan sujith.manoha...@atheros.com
---
drivers/net/wireless/ath/ath9k/Makefile|2 +
drivers/net/wireless/ath/ath9k/htc_drv_debug.c | 219
drivers/net/wireless/ath/ath9k
1 - 100 of 703 matches
Mail list logo