Sujith Manoharan suj...@msujith.org writes:
From: Sujith Manoharan c_man...@qca.qualcomm.com
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/Kconfig | 8 +
drivers/net/wireless/ath/Makefile | 4 +++
drivers/net/wireless/ath/ath.h| 1 +
Kalle Valo wrote:
Why add it to ath.ko module? What drivers are going to use this?
The debug code for ath9k is in ath.ko.
Sujith
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Sujith Manoharan suj...@msujith.org writes:
Kalle Valo wrote:
Why add it to ath.ko module? What drivers are going to use this?
The debug code for ath9k is in ath.ko.
You mean ath_printk() friends? But that doesn't require tracing code
to be in ath.ko as well, right? If I understood
Kalle Valo wrote:
You mean ath_printk() friends? But that doesn't require tracing code
to be in ath.ko as well, right? If I understood correctly, trace.c could
be under ath9k directory and the kconfig option could be
ATH9K_TRACEPOINTS.
I think it's just misleading and confusing for the
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
This gives user-space a normal-ish way to detect that
firmware has failed to start and that a reboot is
probably required.
Signed-off-by: Ben Greear gree...@candelatech.com
[...]
---
From: Ben Greear gree...@candelatech.com
Add support for reading firmware stats through the ethtool
API. This may be easier for applications to manipulate
compared to parsing a text based debugfs file.
kvalo: remove unneeded ifdefs, call ath10k_debug_fw_stats_request() and added
simple error
From: Ben Greear gree...@candelatech.com
kvalo: split into it's own patch, add debugfs file and add locking
Signed-off-by: Ben Greear gree...@candelatech.com
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath10k/core.h |7 +
Kalle Valo kv...@qca.qualcomm.com writes:
From: Ben Greear gree...@candelatech.com
kvalo: split into it's own patch, add debugfs file and add locking
Signed-off-by: Ben Greear gree...@candelatech.com
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
Oh, I forgot to add a commit log. I'm
This patch fixes an issue with rx processing function where we were
decrementing rx_pending count twice.
Patch also queues correct main_work item when rx_pending count reaches
low watermark.
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
A soft lockup was observed on ARM multicore platform while UDP
RX iperf was running on station.
Reason for this is delay_main_task was not taken into consideration while
jumping to process_start. Now if delay_main_task is true, we would exit
mwifiex_main_process instead of going to process_start
SKB lists have their own lock. So this lock is not needed.
Signed-off-by: Avinash Patil pat...@marvell.com
---
drivers/net/wireless/mwifiex/init.c | 1 -
drivers/net/wireless/mwifiex/main.h | 2 --
drivers/net/wireless/mwifiex/pcie.c | 4
drivers/net/wireless/mwifiex/sdio.c | 3 ---
4 files
Michal Kazior michal.kaz...@tieto.com writes:
On 23 September 2014 16:19, Ben Greear gree...@candelatech.com wrote:
On 09/23/2014 02:16 AM, Michal Kazior wrote:
On 19 September 2014 20:28, gree...@candelatech.com wrote:
[...]
+ /* If we are CT firmware, ask it to flush all tids on
Joe Perches j...@perches.com writes:
The return values are not used by callers of these functions
so change the functions to return void.
Other miscellanea:
o add __printf verification to wil6210 logging functions
No format/argument mismatches found
Signed-off-by: Joe Perches
Michal Kazior michal.kaz...@tieto.com writes:
This cleans up and fixes fw stats aggregation.
Michal Kazior (4):
ath10k: split wmi stats parsing
ath10k: rename fw_stats related stuff
ath10k: request fw_stats once on open
ath10k: fix fw stats processing
Thanks, applied.
And thank
On 09/26/14 17:20, Michael Tokarev wrote:
I can send it your way, -- guess it will be quite a bit costly,
but I don't have any use for it anyway (short of throwing it
away), and since I already spent significantly more money due
to all this (whole thinkpad plus ssds and several wifi adaptors),
On Sun, Sep 28, 2014 at 02:30:13PM +0200, Peter Stuge wrote:
Stanislaw Gruszka wrote:
After short chat with Ivo, we decided that I'll take maintenance
of rt2x00 driver.
Thanks for Ivo's great work in the past!
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
I would have been
Unless I can spare some space in rc_stats, v2 will need an increase in
minstrel_debugfs_info buffer (ATM 1 line is 100 chars).
Karl
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 09/29/2014 03:53 AM, Kalle Valo wrote:
Thanks. I think ath10k should do this instead of having CT-specific
flush eventually.
I agree. We should not be forking functionality unless absolutely
necessary.
Ok, this patch is easy to carry in my own tree.
But, for things upstream firmware
On 09/29/2014 01:24 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
This gives user-space a normal-ish way to detect that
firmware has failed to start and that a reboot is
probably required.
Signed-off-by: Ben Greear gree...@candelatech.com
The cycpwr_thr1 value needs to be lower on the extension channel than on
the control channel, similar to how the register settings are programmed
in the initvals.
Also drop the unnecessary check for HT40 - this register can always be
written. This patch has been reported to improve HT40 stability
On AR934x and newer SoC devices, the layout of the AR_RTC_PLL_CONTROL
register changed. This currently breaks at least 5/10 MHz operation.
AR933x uses the old layout.
It might also have been causing other stability issues because of the
different location of the PLL_BYPASS bit which needs to be
This reverts commit 09efc56345be4146ab9fc87a55c837ed5d6ea1ab
I've received reports that this change is decreasing throughput in some
rare conditions on an AR9280 based device
Cc: sta...@vger.kernel.org
Signed-off-by: Felix Fietkau n...@openwrt.org
---
drivers/net/wireless/ath/ath9k/ar5008_phy.c
On 2014-09-29 15:58, Karl Beldan wrote:
You mean having a common hardcoded value for both ?
Yes. And at the same time also getting rid of #if tests for it.
After 4441e8e9 the minstrel rate indexes have to be u8-s and having this
common param 2 would require something like:
{{{
diff --git
On Sat, 2014-09-27 at 16:18 +0800, jammy wrote:
Hi DAN，
1，Are all the SSIDs the same?
A：yes，SSIDs are same.
2，What kind of authentication? WPA Enterprise/802.1x? What EAP methods?
A：there are no authentication，and no EAP methods
3，Is pre-authentication enabled on the network and in the
On Mon, 2014-09-29 at 11:29 +0200, poma wrote:
[platform/nm-platform.c:806] nm_platform_link_set_up(): link: setting up
'wlp0s4f1u1' (4)
[platform/nm-linux-platform.c:2356] link_change_flags(): link: change 4:
flags set 'up' (1)
[platform/nm-linux-platform.c:2250] link_change(): Netlink
On Monday 29 September 2014 15:44:03 Arend van Spriel wrote:
On 09/26/14 17:20, Michael Tokarev wrote:
I can send it your way, -- guess it will be quite a bit costly,
but I don't have any use for it anyway (short of throwing it
away), and since I already spent significantly more money due
As far as I can tell, the .h file is not installed anywhere
in a normal OS.
What is the proper method to get this file sanitized and put
into a more common location?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from
From: Luciano Coelho luciano.coe...@intel.com
The chandef of the channel context a vif is using may be different
than the chandef of the vif itself. For instance, the bandwidth used
by the vif may be narrower than the one configured in the channel
context. To avoid confusion, return the vif's
Sujith Manoharan suj...@msujith.org writes:
Kalle Valo wrote:
You mean ath_printk() friends? But that doesn't require tracing code
to be in ath.ko as well, right? If I understood correctly, trace.c could
be under ath9k directory and the kconfig option could be
ATH9K_TRACEPOINTS.
I think
From: Maithili Hinge maith...@marvell.com
When mwifiex device becomes GO, unicast traffic between client1 and GO stops
when client2 connects to GO. Reason behind this was PTK getting
overwritten by key_material command for client2 as it did not have client
mac address. So, client1 can no more
30 matches
Mail list logo
