On 1 December 2014 at 08:47, Kalle Valo kv...@qca.qualcomm.com wrote:
Michal Kazior michal.kaz...@tieto.com writes:
This will make it easier to extend and maintain
list of supported hardware.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
I fixed a typo: s/whielist/whitelist/
Oops.
From: Luciano Coelho luciano.coe...@intel.com
If the userspace passes a malformed sched scan request (or a net
detect wowlan configuration) by adding a NL80211_ATTR_SCHED_SCAN_MATCH
attribute without any nested matchsets, a NULL pointer dereference
will occur. Fix this by checking that we do
Enable/disable per packet Transmit Power Control (TPC) in lower drivers
according to TX power settings configured by the user. In particular TPC is
enabled if value passed in enum nl80211_tx_power_setting is
NL80211_TX_POWER_AUTOMATIC (no limit from userspace) or
NL80211_TX_POWER_LIMITED (allow
David Miller has marked the patch as Awaiting Upstream, which I
think means that it should be merged through the wireless tree.
Any comment from there?
On Mon, Nov 24, 2014 at 11:19 AM, Ricardo Ribalda Delgado
ricardo.riba...@gmail.com wrote:
The usb gadget driver net2280 has exported a header
Hi John,
here's a pull request I'm hoping still to get to 3.19. The changelog is
below. Please let me know if you have any problems.
--
Only ath10k changes this time and no major changes. Most visible are:
o new debugfs
Assorted fixes
Vladimir Kondratiev (9):
wil6210: propagate disconnect reason
wil6210: add handling of RX HTRSH interrupt
wil6210: fix recovery after scan timeout
wil6210: remove wil_to_pcie_dev()
wil6210: configurable vring sizes
wil6210: fix warning in pointer arithmetic
wil6210:
RX_HTRSH interrupt is handled in exactly the same manner
as RX_DONE interrupt - fetching accumulated packets from RX
ring. In addition there's a rate limitted warning message.
Signed-off-by: Vladimir Kondratiev qca_vkond...@qca.qualcomm.com
---
drivers/net/wireless/ath/wil6210/debug.c | 17
Propagate reason for the disconnect through the relevant call chains:
- report to cfg80211 reason as reported by the firmware
- provide to the firmware reason as requested by cfg80211
Signed-off-by: Vladimir Kondratiev qca_vkond...@qca.qualcomm.com
---
drivers/net/wireless/ath/wil6210/cfg80211.c
Scan timeout treated as indication for firmware error;
and should be handled in the same way.
Recovery state machine does not perform as designed because
its state is not updated in case of scan timeout.
Fix is to set recovery state machine into the proper state.
Signed-off-by: Vladimir
In the wil_tx_ring, error message printed when tx attempted
while vring has no space to accommodate all fragments of frame.
Normally, such situation handled by stopping tx queue.
But, if tx queue is by-passed (like pktgen does), this error
will be triggered at high rate and dmesg will be flooded
Hardware doesn't place any restrictions on the buffer alignment,
consider this TODO resolved.
Signed-off-by: Vladimir Kondratiev qca_vkond...@qca.qualcomm.com
---
drivers/net/wireless/ath/wil6210/txrx.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/ath/wil6210/txrx.c
If card reset with firmware download executed, followed by reset
with use of firmware from build in flash, firmware download indication
remains in the hardware register.
When running firmware download flow,
the SW download indication is written by the driver to bit 0 in usage_6:
wil_fw_load(),
Michal Kazior michal.kaz...@tieto.com writes:
On 27 November 2014 at 10:11, Michal Kazior michal.kaz...@tieto.com wrote:
Latest main firmware branch introduced a new WMI
ABI called wmi-tlv. It is not a tlv strictly
speaking but something that resembles it because
it is ordered and may have
Hi,
here's v3 of Michal's patches to add WMI TLV interface support to
ath10k.
v3:
* add ATH10K_FW_IE_WMI_OP_VERSION
* deprecate ATH10K_FW_FEATURE_WMI_10* feature flags
* remove ATH10K_FW_FEATURE_WMI_TLV, functionality replaced by
ATH10K_FW_IE_WMI_OP_VERSION
* remove struct
It's easier to manage firmware version differences when we configure them in
one place. Rename ath10k_core_init_max_sta_count() to
ath10k_core_init_firmware_features() and start moving most of the firmware
version (features) handling to that function.
Signed-off-by: Kalle Valo
Instead of using feature flags, add new 32 bit variable for managing different
WMI versions. This makes it firmware interface tests a bit less convoluted,
especially when we add one more interface.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath10k/core.c | 30
Better to have this in same place as other firmware interface handling.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath10k/core.c |2 ++
drivers/net/wireless/ath/ath10k/htt_tx.c |5 -
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git
From: Michal Kazior michal.kaz...@tieto.com
This splits the actual event parsing into
intermediary structures to facilitate future
support of vastly different ABI WMI backends.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
From: Michal Kazior michal.kaz...@tieto.com
Since the 10.x fw branch support was introduced it
became apparent ath10k will need to be able to
deal with different fw ABIs eventually.
The patch creates an abstraction for dealing with
command and event structures across different ABIs
and mostly
From: Michal Kazior michal.kaz...@tieto.com
Some functions can be shared across different WMI
ABIs. Make them public so different WMI backends
can use them from different source files in the
future.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
Signed-off-by: Kalle Valo
From: Michal Kazior michal.kaz...@tieto.com
Latest main firmware branch introduced a new WMI
ABI called wmi-tlv. It is not a tlv strictly
speaking but something that resembles it because
it is ordered and may have duplicate id entries.
This prepares ath10k to support new hw.
Signed-off-by:
From: Jonathan Doron j...@wizery.com
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
A self-managed wiphys only employs regulatory information obtained from
the FW and driver and does not use other cfg80211 sources like
beacon-hints,
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
Ilan Peer mentioned this bug privately, so I thought I'd roll it up into
this patch-set
net/wireless/reg.c | 8
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
Signed-off-by: Arik Nemtsov a...@wizery.com
---
nl80211.h | 143 ++
1 file changed, 135 insertions(+), 8 deletions(-)
diff --git a/nl80211.h b/nl80211.h
index f7daae5..9884464 100644
--- a/nl80211.h
+++ b/nl80211.h
@@ -252,7 +252,9 @@
When a phy is given, print only its regdomain. Otherwise, use the newly
implement dump functionality to print all regdomains in the system.
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
index 9af8e7e..a02c982 100644
--- a/reg.c
+++ b/reg.c
@@ -127,7 +127,7 @@ static int print_reg_handler(struct nl_msg *msg, void *arg)
struct nlattr
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
index 9af8e7e..a02c982 100644
--- a/reg.c
+++ b/reg.c
@@ -127,7 +127,7 @@ static int print_reg_handler(struct nl_msg *msg, void *arg)
struct nlattr
Signed-off-by: Arik Nemtsov a...@wizery.com
---
nl80211.h | 143 ++
1 file changed, 135 insertions(+), 8 deletions(-)
diff --git a/nl80211.h b/nl80211.h
index f7daae5..9884464 100644
--- a/nl80211.h
+++ b/nl80211.h
@@ -252,7 +252,9 @@
These were added to cfg80211 recently
Signed-off-by: Arik Nemtsov a...@wizery.com
---
v2: remove XXX from title, apparently the ML doesn't like them :)
reg.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/reg.c b/reg.c
index e1bb0d2..9af8e7e 100644
--- a/reg.c
+++ b/reg.c
@@ -199,6
This patch fix the checkpatch.pl warning:
WARNING: please, no spaces at the start of a line
Signed-off-by: Anjana Sasindran anjanasasindran...@gmail.com
---
drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
When a phy is given, print only its regdomain. Otherwise, use the newly
implement dump functionality to print all regdomains in the system.
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
Signed-off-by: Arik Nemtsov a...@wizery.com
---
info.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/info.c b/info.c
index 7499290..7f8c832 100644
--- a/info.c
+++ b/info.c
@@ -587,6 +587,8 @@ broken_combination:
printf(\tDevice supports WMM-AC admission
On Mon, Dec 01, 2014 at 05:48:44PM +0200, Arik Nemtsov wrote:
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists. Otherwise return the global regdom.
When no wiphy-idx is specified, return the global regdomain as well as
all wiphy-specific
On Mon, Dec 01, 2014 at 05:48:46PM +0200, Arik Nemtsov wrote:
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so
On Mon, Dec 01, 2014 at 05:48:47PM +0200, Arik Nemtsov wrote:
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
Luis
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists. Otherwise return the global regdom.
When no wiphy-idx is specified, return the global regdomain as well as
all wiphy-specific regulatory domains in the system, via a new nested
list of attributes.
From: Jonathan Doron j...@wizery.com
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
A self-managed wiphys only employs regulatory information obtained from
the FW and driver and does not use other cfg80211 sources like
beacon-hints,
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
---
net/wireless/reg.c | 8 +++-
1 file changed, 7 insertions(+), 1
On 12/01/2014 09:53 AM, Anjana Sasindran wrote:
This patch fix the checkpatch.pl warning:
WARNING: please, no spaces at the start of a line
Signed-off-by: Anjana Sasindran anjanasasindran...@gmail.com
---
drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c | 6 +++---
1 file changed, 3
On Mon, 2014-12-01 at 21:23 +0530, Anjana Sasindran wrote:
This patch fix the checkpatch.pl warning:
WARNING: please, no spaces at the start of a line
[]
diff --git a/drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c
b/drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c
[]
@@ -20,7 +20,7 @@
On Mon, Dec 01, 2014 at 06:28:48PM +0200, Arik Nemtsov wrote:
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists. Otherwise return the global regdom.
When no wiphy-idx is specified, return the global regdomain as well as
all wiphy-specific
On Mon, Nov 10, 2014 at 12:12 PM, Brent Taylor moto...@gmail.com wrote:
Resending in plain text mode...
Hi Kalle,
I have a custom built board with an AR6003 WiFi chip running
linux-3.10.40 and hostapd 2.2 that I'm trying to use as an access
point.
My configuration file for hostapd is:
On Tue, Dec 2, 2014 at 12:19 AM, Brent Taylor moto...@gmail.com wrote:
On Mon, Nov 10, 2014 at 12:12 PM, Brent Taylor moto...@gmail.com wrote:
Resending in plain text mode...
Hi Kalle,
I have a custom built board with an AR6003 WiFi chip running
linux-3.10.40 and hostapd 2.2 that
Did you check the wireless-next tree's git logs?
commit a831f20b6d6460640b83644d1c1df6e7e8ca9f68
Author: Ricardo Ribalda Delgado ricardo.riba...@gmail.com
Date: Mon Nov 24 11:19:51 2014 +0100
wireless/p54: Remove duplicated net2280 header
The usb gadget driver net2280 has exported
Hello John
No sorry. I only checked patchwork and the mailing list. I was
expecting the typical mail when a patch is merged into a tree :),
sorry about that, first contrib to the wireless subsystem.
Thanks
On Mon, Dec 1, 2014 at 8:59 PM, John W. Linville linvi...@tuxdriver.com wrote:
Did you
On Thu, Nov 27, 2014 at 12:36:06PM +0200, Johan Hedberg wrote:
Hi John,
Here's one more bluetooth-next pull request for 3.19:
- Minor cleanups for ieee802154 mac802154
- Fix for the kernel warning with !TASK_RUNNING reported by Kirill A.
Shutemov
- Support for another ath3k device
On Mon, Dec 01, 2014 at 02:42:41PM +0200, Kalle Valo wrote:
Hi John,
here's a pull request I'm hoping still to get to 3.19. The changelog is
below. Please let me know if you have any problems.
--
Only ath10k changes this
Hi Arend,
sorry for my late reply, it took me a bit to get the modules compiled with
your patches. Here is the information from my card. During this test I had
very bad performance with my wifi connection with big latency and lots of
packet loss.
[ 1642.407735] bcma: bus0: Found chip with id
All,
I work for the prpl Foundation, an open source foundation organized by
a number of companies, most related to MIPS. One project we work with
externally is the OpenWrt project. Recently one of our members
mentioned a new FCC requirement (described in FCC publication 594280)
which requires
On Mon, Dec 01, 2014 at 04:27:25PM -0600, Eric Schultz wrote:
All,
I work for the prpl Foundation, an open source foundation organized by
a number of companies, most related to MIPS. One project we work with
externally is the OpenWrt project. Recently one of our members
mentioned a new FCC
On Mon, 2014-12-01 at 15:33 +0200, Vladimir Kondratiev wrote:
In addition there's a rate limitted warning message.
limited.
I think this _ratelimited bit should be a separate patch.
(and a suggestion / comment below too)
diff --git a/drivers/net/wireless/ath/wil6210/debug.c
Am 02.12.2014 um 01:31 schrieb John W. Linville:
On Mon, Dec 01, 2014 at 04:27:25PM -0600, Eric Schultz wrote:
All,
I work for the prpl Foundation, an open source foundation organized by
a number of companies, most related to MIPS. One project we work with
externally is the OpenWrt project.
On 1 December 2014 at 15:46, Kalle Valo kv...@qca.qualcomm.com wrote:
[...]
diff --git a/drivers/net/wireless/ath/ath10k/core.c
b/drivers/net/wireless/ath/ath10k/core.c
index b1cb90bb4c1c..ac7fbe8605bc 100644
--- a/drivers/net/wireless/ath/ath10k/core.c
+++
On 1 December 2014 at 15:44, Kalle Valo kv...@qca.qualcomm.com wrote:
[...]
int ath10k_core_start(struct ath10k *ar, enum ath10k_firmware_mode mode)
@@ -1046,7 +1047,12 @@ static int ath10k_core_probe_fw(struct ath10k *ar)
return ret;
}
-
Michal Kazior michal.kaz...@tieto.com writes:
On 1 December 2014 at 15:44, Kalle Valo kv...@qca.qualcomm.com wrote:
[...]
int ath10k_core_start(struct ath10k *ar, enum ath10k_firmware_mode mode)
@@ -1046,7 +1047,12 @@ static int ath10k_core_probe_fw(struct ath10k *ar)
return
This can happen and there is no point in added more
detection code lower in the stack. Catching these in one
single point (cfg80211) is enough. Stop WARNING about this
case.
This fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=89001
Cc: sta...@vger.kernel.org
Fixes: 2f1c6c572d7b (cfg80211:
58 matches
Mail list logo
