This patch enables MU-MIMO transmit beamforming support
for QCA99X0 chipsets.
Signed-off-by: Vivek Natarajan
---
drivers/net/wireless/ath/ath10k/mac.c | 44 +++
drivers/net/wireless/ath/ath10k/wmi.h | 5
2 files changed, 49 insertions(+)
diff --git a/driver
qca61x4 uses the vdev param as a sole sufficient configuration
for txbf while qca99x0 enables txbf during peer assoc by
combining the vdev param value with peer assoc's vht capabilities
This patch gets the appropriate txbf configuration scheme
before passing the wmi command to enable the same in t
remove spaces at the start of a line
align enum variable with other parameters
Signed-off-by: Ting-Chih Hsiao
---
drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c
b/drivers/s
On Tue, Aug 4, 2015 at 9:26 AM, Chen-Yu Tsai wrote:
> On Tue, Aug 4, 2015 at 2:27 AM, Seth Forshee
> wrote:
>> On Thu, Jul 23, 2015 at 11:32:56AM +0800, Chen-Yu Tsai wrote:
>>> Taiwan's Ministry of Transportation and Communications revised its
>>> frequency allocation rules [1] on 2014/11/17, al
On Tue, Aug 4, 2015 at 2:34 AM, Seth Forshee wrote:
> On Thu, Jul 23, 2015 at 11:32:59AM +0800, Chen-Yu Tsai wrote:
>> The FCC increased the maximum conducted transmission power for the
>> U-NII-1 (5150 ~ 5250 MHz) band to 30 dBm or 1 W for master devices
>> and 24 dBm or 250 mW for mobile/portabl
On Tue, Aug 4, 2015 at 2:27 AM, Seth Forshee wrote:
> On Thu, Jul 23, 2015 at 11:32:56AM +0800, Chen-Yu Tsai wrote:
>> Taiwan's Ministry of Transportation and Communications revised its
>> frequency allocation rules [1] on 2014/11/17, allowing usage of 5600 ~
>> 5650 MHz, previously allocated to w
On Sun, Aug 02, 2015 at 09:23:51PM +0530, Chandra S Gorentla wrote:
> Added 'void' keyword in the paranthesis of function definitions, when
> there are no arguments to the functions. This fixes the checkpatch.pl
> error - "Bad function definition 'function()' should probably be
> function(void)".
Hi all,
Today I’ve released my WiFi register monitoring tool RegMon on GitHub:
https://github.com/thuehn/RegMon
RegMon consists of Atheros driver patches to monitor arbitrary registers under
ath9k, ath5k and madwifi from user space with high sampling rates (up to
~20kHz). My common research us
In this driver, two variables are masked by one quantity, and then tested
against a second number with more bits that the mask. Accordingly, the
test always fails. To minimize the possibility of such typos, a symbolic
definition of the mask is created and used.
The separate load and mask operation
This driver is converted to use the common firmware header struct.
Because the old header definition failed to indicate that the multi-byte
entries should be little endian, several problems were thus exposed.
These are fixed.
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8821ae
This driver is converted to use the common firmware header struct.
Because the old header definition failed to indicate that the multi-byte
entries should be little endian, several problems were thus exposed.
These are fixed.
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8188ee
This driver is converted to use the common firmware header struct.
Because the old header definition failed to indicate that the multi-byte
entries should be little endian, several problems were thus exposed.
These are fixed.
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8192de
Commit e996db69833a (rtlwifi: rtl8192c: Add init codes for "fw_version"
and "fw_subversion") added initialization for fw_version, but failed to
note that the variable in the firmware header is little-endian. The
following Sparse warning results:
CHECK drivers/net/wireless/rtlwifi/rtl8192c/fw_c
The drivers are converted to use the common firmware header struct.
Because the old header definition failed to indicate that the multi-byte
entries should be little endian, several problems were thus exposed.
These are fixed.
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8723a
While fixing an endian issue introduced in commit e996db69833a,
I realized that there were similar endian issues in several
of the drivers. In addition, these drivers were all defining a
similar struct. A single common definition is moved into the
main header, and all drivers are converted to use
This driver is converted to use the common firmware header struct.
Because the old header definition failed to indicate that the multi-byte
entries should be little endian, several problems were thus exposed.
These are fixed.
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8192ee
From: pkshih
Use the new capability in rtlwifi to prevent rekeying before EAPOL msg 4/4
has been sent.
Signed-off-by: pkshih
Signed-off-by: shaofu
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8821ae/trx.c | 8
drivers/net/wireless/rtlwifi/rtl8821ae/trx.h | 13 +++
From: pkshih
Use the new capability in rtlwifi to prevent rekeying before EAPOL msg 4/4
has been sent.
Signed-off-by: pkshih
Signed-off-by: shaofu
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8723be/fw.c | 1 +
drivers/net/wireless/rtlwifi/rtl8723be/trx.c | 8
From: pkshih
When connected, the drivers will use EAPOL to do PTK rekey. When msg 3/4 is
received, the supplicant will send msg 4/4 and install new key immediately.
However, the driver must make sure that msg 4/4 is sent before it installs
the new key. A new routine is created to ensure that msg
From: pkshih
Making the retry limits depend on the vif type can boost performance.
Signed-off-by: pkshih
Signed-off-by: shaofu
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/core.c | 19 +++
drivers/net/wireless/rtlwifi/pci.c | 8 +++-
drivers/net/wireless
From: pkshih
Use the new capability in rtlwifi to prevent rekeying before EAPOL msg 4/4
has been sent.
Signed-off-by: pkshih
Signed-off-by: shaofu
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8192ee/fw.c | 1 +
drivers/net/wireless/rtlwifi/rtl8192ee/trx.c | 8
2
From: pkshih
There is a potential race condition when the control byte of a CAM entry
is written first.
Signed-off-by: pkshih
Signed-off-by: shaofu
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/cam.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/dri
From: timlee
The 5G channel list contains channels that are not supported.
Signed-off-by: timlee
Signed-off-by: shaofu
Signed-off-by: Larry Finger
---
drivers/net/wireless/rtlwifi/rtl8821ae/hw.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wi
The Realtek engineers have suggested several improvements to this family
of drivers. The changes include:
1. Fix the 5G channel assignments to remove unused channels.
2. Fix a potential race condition when updating CAM.
3. Change retry limits to depend on vif type.
4. Fix a race condition that cou
On Mon, Aug 03, 2015 at 01:34:22PM -0500, Seth Forshee wrote:
> On Thu, Jul 23, 2015 at 11:32:59AM +0800, Chen-Yu Tsai wrote:
> > The FCC increased the maximum conducted transmission power for the
> > U-NII-1 (5150 ~ 5250 MHz) band to 30 dBm or 1 W for master devices
> > and 24 dBm or 250 mW for mo
On Thu, Jul 23, 2015 at 11:32:58AM +0800, Chen-Yu Tsai wrote:
> Taiwan's Ministry of Transportation and Communications revised its
> frequency allocation rules [1] on 2014/11/17, opening up 5150 ~ 5250
> MHz to U-NII applications.
>
> Taiwan's regulatory body, NCC, officially stated [3][4] that un
On Thu, Jul 23, 2015 at 11:32:59AM +0800, Chen-Yu Tsai wrote:
> The FCC increased the maximum conducted transmission power for the
> U-NII-1 (5150 ~ 5250 MHz) band to 30 dBm or 1 W for master devices
> and 24 dBm or 250 mW for mobile/portable devices.
>
> Effective 6/2/2014.
>
> See FCC KDB 90546
On Thu, Jul 23, 2015 at 11:32:56AM +0800, Chen-Yu Tsai wrote:
> Taiwan's Ministry of Transportation and Communications revised its
> frequency allocation rules [1] on 2014/11/17, allowing usage of 5600 ~
> 5650 MHz, previously allocated to weather radars, to U-NII applications
> with DFS support.
>
tree:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
master
head: 9a2f971eee40039d09458580a87515cb540688c2
commit: 7d96eee8472d80d72510d3c7cf9de3703ed7ad56 [10/12] Merge branch 'master'
of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
config: x86_6
Ting-Chih Hsiao writes:
> remove spaces at the start of a line
> align enum variable with other parameters
>
> Signed-off-by: Ting-Chih Hsiao
> ---
> drivers/staging/rtl8723au/hal/odm_RegConfig8723A.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl872
Make ath_opmode_to_string return "OCB" for NL80211_IFTYPE_OCB. Currently
it will return "UNKNOWN".
Signed-off-by: Bertold Van den Bergh
---
drivers/net/wireless/ath/debug.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/debug.c b/drivers/net/wi
Hello there,
[linux-4.2-rc5/drivers/net/wireless/rtlwifi/rtl8192c/dm_common.c:1542] ->
[linux-4.2-rc5/drivers/net/wireless/rtlwifi/rtl8192c/dm_common.c:1545]: (style)
Mismatching assignment and comparison, comparison 'bt_pri==4294967295' is
always false.
bt_pri = bt_pri & 0x00ff;
i
Hi Paul,
> > + int ret;
> > + int chid;
> > + u8 null_ssid[IEEE80211_MAX_SSID_LEN] = {0};
>
> Alas, this is not the only form of "hidden SSID". This behavior is not
> standardized. You need to either expand your search to other hidden
> SSID signatures (zero-length SSID, all-n
Even though there's a WMI enum for fragmentation
threshold no known firmware actually implements
it. Moreover it is not possible to rely frame
fragmentation to mac80211 because firmware clears
the "more fragments" bit in frame control making
it impossible for remote devices to reassemble
frames.
H
Commit 1010ba4c5d1c ("ath10k: unregister and
remove frag_threshold callback") didn't remove all
instances of (futile) fragmentation threshold
configuration. No known firmware supports the
parameter so don't even bother setting it.
Signed-off-by: Michal Kazior
---
drivers/net/wireless/ath/ath10k/
If driver failed to setup wiphy params (e.g. rts
threshold, fragmentation treshold) userspace
wasn't properly notified about this. This could
lead to user confusion who would think the command
succeeded even if that wasn't the case.
Signed-off-by: Michal Kazior
---
net/wireless/nl80211.c | 1 +
> The driver code allows for the disabling of MSI interrupts; however the
> module_parm line was missed and the option fails to show with modinfo.
>
> Signed-off-by: Larry Finger
> Cc: Stable [3.15+]
Thanks, applied to wireless-drivers.git.
Kalle Valo
--
To unsubscribe from this list: send th
37 matches
Mail list logo
