gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
We will need to use these in set-antenna, so move them
so that we do not have to define the method signatures.
Signed-off-by: Ben Greear gree...@candelatech.com
I'm dropping these two patches. Please resend once we
Kalle Valo kv...@qca.qualcomm.com writes:
+static ssize_t ath10k_reg_value_read(struct file *file,
+ char __user *user_buf,
+ size_t count, loff_t *ppos)
+{
+ struct ath10k *ar = file-private_data;
+ u8 buf[48];
+
Kalle Valo kv...@qca.qualcomm.com writes:
+static ssize_t ath10k_mem_value_read(struct file *file,
+ char __user *user_buf,
+ size_t count, loff_t *ppos)
+{
+ struct ath10k *ar = file-private_data;
+ u8 *buf;
+
On 25 November 2014 at 09:41, Kalle Valo kv...@qca.qualcomm.com wrote:
Kalle Valo kv...@qca.qualcomm.com writes:
+static ssize_t ath10k_mem_value_read(struct file *file,
+ char __user *user_buf,
+ size_t count, loff_t *ppos)
Michal Kazior michal.kaz...@tieto.com writes:
--- a/drivers/net/wireless/ath/ath10k/htt_rx.c
+++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
@@ -1381,6 +1381,8 @@ static bool ath10k_htt_rx_amsdu_allowed(struct ath10k
*ar,
{
struct sk_buff *msdu;
struct htt_rx_desc *rxd;
+
On 25 November 2014 at 10:04, Kalle Valo kv...@qca.qualcomm.com wrote:
Michal Kazior michal.kaz...@tieto.com writes:
[...]
@@ -1394,12 +1396,19 @@ static bool ath10k_htt_rx_amsdu_allowed(struct
ath10k *ar,
return false;
}
+ is_mgmt = !!(rxd-attention.flags
+
Michal Kazior michal.kaz...@tieto.com writes:
On 25 November 2014 at 10:04, Kalle Valo kv...@qca.qualcomm.com wrote:
Michal Kazior michal.kaz...@tieto.com writes:
[...]
@@ -1394,12 +1396,19 @@ static bool ath10k_htt_rx_amsdu_allowed(struct
ath10k *ar,
return false;
}
On 11/24/14 22:53, John W. Linville wrote:
I am holding patches 2-4 until we resolve the brcmu_boardrev_str
build thing...
Actually, only patch 2 and 3 are related to the build thing. If that is
what this is.
Regards,
Arend
On Thu, Nov 20, 2014 at 10:27:00PM +0100, Arend van Spriel wrote:
From: Yanbo Li yan...@qti.qualcomm.com
Add mem_val debugfs file for dumping the firmware (target) memory and also for
writing to the memory. The firmware memory is accessed through one file which
uses position of the file as the firmware memory address. For example, with dd
use skip parameter for
Hi,
this is v3 of Yanbo's firmware memory debugfs interface.
Changelog:
v3:
* check ath10k state and return an error if firmware is not running
* switch to use conf_mutex because using ar-state
* fix copy_from_user() error handling
v2:
* split patches into two
* simplify the commit logs
On Tue, Nov 25, 2014 at 6:23 PM, Johannes Berg
johan...@sipsolutions.net wrote:
From: Johannes Berg johannes.b...@intel.com
If there are no channels allowing 80 MHz to be used, then the
station isn't really VHT capable even if the driver and device
support it in general. In this case, exclude
On Tue, 2014-11-25 at 19:00 +0800, YanBo wrote:
On Tue, Nov 25, 2014 at 6:23 PM, Johannes Berg
johan...@sipsolutions.net wrote:
From: Johannes Berg johannes.b...@intel.com
If there are no channels allowing 80 MHz to be used, then the
station isn't really VHT capable even if the driver
On Tue, Nov 25, 2014 at 7:04 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Tue, 2014-11-25 at 19:00 +0800, YanBo wrote:
On Tue, Nov 25, 2014 at 6:23 PM, Johannes Berg
johan...@sipsolutions.net wrote:
From: Johannes Berg johannes.b...@intel.com
If there are no channels allowing 80
Hi all,
The AP role can manage several sta.
In case of WMM, each sta have a separate queue or all sta use the same
queue?
Where can I found any information on the WMM queue management in linux
wireless?
I'm using ath9k driver.
Cedric Voncken
--
To unsubscribe from this list: send the line
On Tue, 2014-11-25 at 19:10 +0800, YanBo wrote:
We already start the working to support the VHT modulations MCS8 and
MCS9 support in 2.4G for ath10k devices,
and it used the band-vht_cap = vht_cap to notification the mac80211,
if we band it with 80MHz, it is do need another
new
On 11/24/14 22:50, John W. Linville wrote:
Hmmm...I'm not sure why, but this is causing problems for me...
ERROR: brcmu_boardrev_str
[drivers/net/wireless/brcm80211/brcmsmac/brcmsmac.ko] undefined!
I am confused as well. I did not have such an issue. The function is
provided by brcmutil.ko
On Fri, Nov 21, 2014 at 10:39:39AM +0100, Ronald Wahl wrote:
For me the patch will work but there is a change for RT3290 and RT5390. On
both chipsets BBP 1 was not written before but with this patch it is going
to be written now and the value depends on the return of
On Tue, Nov 25, 2014 at 8:07 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Tue, 2014-11-25 at 19:10 +0800, YanBo wrote:
We already start the working to support the VHT modulations MCS8 and
MCS9 support in 2.4G for ath10k devices,
and it used the band-vht_cap = vht_cap to notification
This prevents warning spamming if peer creation
fails during sta_state in some cases.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/mac.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/mac.c
The number of peers isn't directly translatable to
the number of stations because ath10k needs to
reserve a few extra peers for special cases like
multi-vif concurrency.
The previous limit was 126 and 15 stations in AP
mode for 10.x and main firmware branches
respectively. The limit is now 128
This patchset includes couple of fixes, delay work queue logic
removal for USB interface and Tx status support work.
Amitkumar Karwar (5):
mwifiex: fix sparse warning
mwifiex: fix scan problem on big endian platforms
mwifiex: skip delay main work logic for USB interface.
mwifiex: add Tx
We had introduced delay main work logic to avoid processing
interrupts when Rx pending packet count reaches high threshold.
interrupt processing is restarted later when packet count
reduces lower threashold. This helped to reduce unnecessary
overhead and improve throughput for SD and PCIe
This patch adds missing endian conversion for beacon size while
processing scan response.
Reported-by: Daniel Mosquera daniel.mosqu...@ctag.com
Tested-by: Daniel Mosquera daniel.mosqu...@ctag.com
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Amitkumar Karwar akar...@marvell.com
Firmware notifies the driver through event if EAPOL data packet
has been acked or not. We will inform this status to userspace
listening on a socket.
Signed-off-by: Cathy Luo c...@marvell.com
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Amitkumar Karwar akar...@marvell.com
---
ACK status (0/1) for ACTION frames is informed to cfg80211. We
will extend existing logic used for EAPOL frames. The cfg80211
API is different here. Also, we need to explicitly free cloned
skb.
Signed-off-by: Cathy Luo c...@marvell.com
Signed-off-by: Avinash Patil pat...@marvell.com
On Tue, Nov 25, 2014 at 10:18 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Tue, 2014-11-25 at 22:13 +0800, YanBo wrote:
But is all of that really the right way? I'm not completely convinced.
Except set the flag, the HW itself should support this feature, or
else it also doesn't
Currently implemented temperature compensation is only valid on some of
supported chips. Other chips do not need temperature compensation or
need different way to do this (not yet implemented in the rt2800
driver). Trying to do run rt2800_get_gain_calibration_delta() when this
is not appropriate
On 11/25/14 15:18, Johannes Berg wrote:
On Tue, 2014-11-25 at 22:13 +0800, YanBo wrote:
But is all of that really the right way? I'm not completely convinced.
Except set the flag, the HW itself should support this feature, or
else it also doesn't work, I'd
send the patch in soon for public
Agree with you that it need a bigger discussion about whether
advertise VHT is the suitable/best
way to support the VHT at 2.4G feature.
We are considered this ways as it is already be used by some vendor
like BRCM or Qualcomm Atheros
in there full mac product, and there will be IOT
These two patches are needed to fix a regression introduced when
driver rtl8821ae was moved from staging to the regular wireless tree.
I am sorry that these fixes are so late in the 3.18 cycle.
Larry
Larry Finger (2):
rtlwifi: rtl8821ae: Fix 5G detection problem
rtlwifi: Change order in
The existing order of steps when starting the PCI devices works for
2.4G devices, but fails to initialize the 5G section of the RTL8821AE
hardware.
This patch is needed to fix the regression reported in Bug #88811
(https://bugzilla.kernel.org/show_bug.cgi?id=88811).
Reported-by: Valerio Passini
Dear Sir/Madam,
I'm working on a project in which we need to set and get RF sensitivity of WLAN
device. I tried to set other settings such as operation mode, txpower and
frequency using Linux commands : ioctl and iwconfig and it works fine.
Manufacturer of my device is Broadcom. It seems that
On Tue, Nov 25, 2014 at 02:00:38PM +0100, Arend van Spriel wrote:
On 11/25/14 13:12, Arend van Spriel wrote:
On 11/24/14 22:50, John W. Linville wrote:
Hmmm...I'm not sure why, but this is causing problems for me...
ERROR: brcmu_boardrev_str
On Tue, Nov 25, 2014 at 11:01:47AM +0100, Arend van Spriel wrote:
On 11/24/14 22:53, John W. Linville wrote:
I am holding patches 2-4 until we resolve the brcmu_boardrev_str
build thing...
Actually, only patch 2 and 3 are related to the build thing. If that is what
this is.
OK, I won't
On 11/25/14 20:05, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:49:45PM -0500, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:12:34PM +0100, Arend van Spriel wrote:
On 11/24/14 22:50, John W. Linville wrote:
Hmmm...I'm not sure why, but this is causing problems for me...
ERROR:
On 11/25/14 20:16, Arend van Spriel wrote:
On 11/25/14 20:05, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:49:45PM -0500, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:12:34PM +0100, Arend van Spriel wrote:
On 11/24/14 22:50, John W. Linville wrote:
Hmmm...I'm not sure why, but
On 11/25/14 20:23, Arend van Spriel wrote:
On 11/25/14 20:16, Arend van Spriel wrote:
On 11/25/14 20:05, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:49:45PM -0500, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:12:34PM +0100, Arend van Spriel wrote:
On 11/24/14 22:50, John W.
On Tue, Nov 25, 2014 at 08:16:17PM +0100, Arend van Spriel wrote:
On 11/25/14 20:05, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:49:45PM -0500, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:12:34PM +0100, Arend van Spriel wrote:
On 11/24/14 22:50, John W. Linville wrote:
On Sun, Nov 23, 2014 at 05:02:20PM +0200, Arik Nemtsov wrote:
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
On 11/25/14 20:20, John W. Linville wrote:
On Tue, Nov 25, 2014 at 08:16:17PM +0100, Arend van Spriel wrote:
On 11/25/14 20:05, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:49:45PM -0500, John W. Linville wrote:
On Tue, Nov 25, 2014 at 01:12:34PM +0100, Arend van Spriel wrote:
On
The hardware info now also include radio and phy information, which
can be helpful in debugging issues.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
On Sun, Nov 23, 2014 at 05:02:21PM +0200, Arik Nemtsov wrote:
From: Jonathan Doron j...@wizery.com
Allow usermode to query wiphy-specific regd info, for drivers that use
wiphy-specific regulatory management.
Use the existing API for sending regdomain info to usermode, but return
the
The changes associated with moving this driver from staging to the regular
tree missed one section setting the allowable rates for the 5GHz band.
This patch is needed to fix the regression reported in Bug #88811
(https://bugzilla.kernel.org/show_bug.cgi?id=88811).
Reported-by: Valerio Passini
On 25 November 2014 at 20:55, Arend van Spriel ar...@broadcom.com wrote:
+/* Produce a human-readable string for boardrev */
+char *brcmu_boardrev_str(u32 brev, char *buf)
+{
+ char c;
+
+ if (brev 0x100) {
+ snprintf(buf, 8, %d.%d, (brev 0xf0) 4, brev 0xf);
+
From: Bing Zhao bz...@marvell.com
This patch adds new API to handle scatter gather aggregation.
Signed-off-by: Bing Zhao bz...@marvell.com
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Xinming Hu h...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
It appears it takes more than just setting the
hardware's chainmask to make things work well. Without
this patch, a vdev would only use 1x1 rates when chainmask
was set to 0x3.
Setting the 'nss' (number of spatial
Michal Kazior michal.kaz...@tieto.com writes:
New firmware revisions don't need peer creation
when doing offchannel tx. Earlier revisions would
queue and never release frames without a peer.
This prevent new firmware revisions from stopping
replenishing wmi-htc tx credits and improves
Michal Kazior michal.kaz...@tieto.com writes:
Some firmware revisions don't seem to deilver
management frames with FCS error via WMI so narrow
down the HTT rule to not drop corrupted management
frames.
This basically increases number of frames ath10k
reports while sniffing.
Sujith Manoharan suj...@msujith.org writes:
From: Sujith Manoharan c_man...@qca.qualcomm.com
When static keys are used in shared WEP, when a
station is associated, message 3 is sent with an
encrypted payload. But, for subsequent
authentications that are triggered without a
deauth, the auth
Michal Kazior michal.kaz...@tieto.com writes:
This will make it easier to extend and maintain
list of supported hardware.
As a requirement this moves chip_id checking a
little later because target_version isn't known
until BMI can be queried.
Signed-off-by: Michal Kazior
On 26 November 2014 at 08:21, 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.
As a requirement this moves chip_id checking a
little later because target_version isn't known
51 matches
Mail list logo