It's clear from the indenting that curly braces were intended here.
Fixes: e35000ead491 ('mwifiex: preprocess packets from TX queue')
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/net/wireless/mwifiex/txrx.c
b/drivers/net/wireless/mwifiex/txrx.c
index
From: Luciano Coelho luciano.coe...@intel.com
Just clarify that the delay is only before the first cycle.
Signed-off-by: Luciano Coelho luciano.coe...@intel.com
---
include/uapi/linux/nl80211.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/nl80211.h
On Wed, 2015-03-18 at 11:36 +0200, Eliad Peller wrote:
On Tue, Mar 17, 2015 at 7:58 PM, Emmanuel Grumbach
emmanuel.grumb...@intel.com wrote:
From: David Spinadel david.spina...@intel.com
Stop scan before authentication or association to make sure
that nothing interferes with connection
This will expose in /sys whether the ifname of a device is set by userspace
or generated by the kernel. The latter kind (wlanX, etc) is not deterministic,
so userspace needs to rename these devices to names that are guaranteed to
stay the same between reboots. The former, however should never be
With patch '960d6d08e39 mwifiex: delay skb allocation for RX
until cmd53 over' we no more pass skb parameter to MP aggregation setup
helper function. We instead pass length to be aggregated.
This patch fixes an issue where we were passing length parameter of NULL
skb to aggregation routine
On Tue, Mar 17, 2015 at 7:58 PM, Emmanuel Grumbach
emmanuel.grumb...@intel.com wrote:
From: David Spinadel david.spina...@intel.com
Stop scan before authentication or association to make sure
that nothing interferes with connection flow.
this makes sense
Currently mac80211 defers RX auth
On Wed, Mar 18, 2015 at 11:46 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2015-03-18 at 11:36 +0200, Eliad Peller wrote:
On Tue, Mar 17, 2015 at 7:58 PM, Emmanuel Grumbach
emmanuel.grumb...@intel.com wrote:
From: David Spinadel david.spina...@intel.com
Stop scan before
Kyle McMartin k...@infradead.org writes:
On Thu, Mar 12, 2015 at 01:35:12PM +0200, Kalle Valo wrote:
This is the latest firmware from 10.2.4 firmware branch.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
Pardon my ignorance... It looks like your driver needs more than just
On Mon, Mar 16, 2015 at 05:41:00PM +0100, Sebastian Andrzej Siewior wrote:
* Kalle Valo | 2015-03-16 16:06:52 [+]:
Thanks, 3 patches applied to wireless-drivers-next.git:
Thanks. Do you guys have any kind of further documentation? Where did
There is doc describing MAC registers, it was
This patch added support for the BCM43430 802.11n SDIO chipset.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Daniel (Deognyoun) Kim de...@broadcom.com
Reviewed-by: Franky (Zhenhui) Lin fran...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by:
From: Hante Meuleman meule...@broadcom.com
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Hante Meuleman meule...@broadcom.com
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
Several host controllers supporting runtime-pm are causing issues
with our sdio wireless cards because they disable the sdio interrupt
upon going into runtime suspend. This patch avoids that by doing
a pm_runtime_forbid() call during the probe. Tested with Sony Vaio
Duo 13 which uses sdhci-acpi
From: Hante Meuleman meule...@broadcom.com
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Hante Meuleman meule...@broadcom.com
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
This series adds support for the BCM43430 SDIO chipset. Recent
BCM4345 support is changed to support BCM43455 and BCM43457 as
it has been verified on those. In SDIO driver part memory barriers
have been added to assure data validity between driver threads.
This series is intended for v4.1 kernel
Recently support was added for the BCM4345 SDIO chipset by
commit 9c51026509d7 (brcmfmac: Add support for BCM4345 SDIO chipset)
however this was verified using a BCM43455 device, which is
a more recent revision of the chip. This patch assure that
older revisions are not probed as they would fail.
The BCM4356 PCIe wireless device was added recently but overlooked
the fact that the MODULE_FIRMWARE() macros were missing for the
firmwares needed by this device.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Arend van
There are no known BCM4354 PCIe devices released so removing
support from the driver until proven otherwise.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
From: Luciano Coelho l...@coelho.fi
Instead of defining an enumeration with the FW specific values for the
different clock rates, use the actual frequency instead. Also add a
boolean to specify whether the clock is XTAL or not.
Change all board files to reflect this.
Signed-off-by: Luciano
When running with device-tree, we no longer have a board file
that can set up the platform data for wlcore.
Allow this data to be passed from DT.
Signed-off-by: Ido Yariv i...@wizery.com
Signed-off-by: Eliad Peller el...@wizery.com
Tested-by: Sébastien Szymanski sebastien.szyman...@armadeus.com
Add device tree binding documentation for TI's wilink
(wl12xx and wl18xx) wlan chip.
Signed-off-by: Eliad Peller el...@wizery.com
---
.../devicetree/bindings/net/wireless/ti,wlcore.txt | 47 ++
1 file changed, 47 insertions(+)
create mode 100644
Now that we have wlcore device-tree bindings in place
(for both wl12xx and wl18xx), remove the legacy
wl12xx_platform_data struct, and move its members
into the platform device data (that is passed to wlcore)
Davinci 850 is the only platform that still set
the platform data in the legacy way (and
On Wed, Mar 18, 2015 at 10:42:12AM +0200, Kalle Valo wrote:
Kyle McMartin k...@infradead.org writes:
On Thu, Mar 12, 2015 at 01:35:12PM +0200, Kalle Valo wrote:
This is the latest firmware from 10.2.4 firmware branch.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
Pardon my
Now that ANI is enabled by default, allow user to disable or enable ANI feature
from debugfs
Signed-off-by: Ashok Raj Nagarajan arnag...@qti.qualcomm.com
---
drivers/net/wireless/ath/ath10k/core.h | 1 +
drivers/net/wireless/ath/ath10k/debug.c | 58 +
On 03/18/15 20:18, Johannes Berg wrote:
Hi Arend,
Is it ok to update the wiphy band information after registration.
I believe this will cause issues.
In
brcmfmac the firmware is queried to obtain the supported channels.
However, it returns the channels for the current country set in
On Wed, 2015-03-18 at 07:44 +0100, Nicholas Mc Guire wrote:
On Tue, 17 Mar 2015, Joe Perches wrote:
On Tue, 2015-03-17 at 08:06 -0400, Nicholas Mc Guire wrote:
Converting milliseconds to jiffies by val * HZ / 1000 is technically
OK but msecs_to_jiffies(val) is the cleaner solution and
As the subject indicates, adjust whitespace in and around comments
in rtl8723au's rtw_security.c.
Signed-off-by: M. Vefa Bicakci m@runbox.com
---
drivers/staging/rtl8723au/core/rtw_security.c | 114 +-
1 file changed, 57 insertions(+), 57 deletions(-)
diff --git
Prior to this commit, functions rtw_tkip_encrypt23a and rtw_tkip_decrypt23a had
large if blocks which contained the majority of the logic in the functions.
Rework these functions so that if the negated version of the aforementioned if
blocks' conditions are true, we return from the function with
This commit removes a number of unneeded comments. Two of the
aforementioned comments were most likely meant to aid with version
control, whereas the remaining two comments relate to (now unused)
local variable names.
Signed-off-by: M. Vefa Bicakci m@runbox.com
---
Prior to this commit, rtl8723au's rtw_security.c had two instances of
byte array comparisons (for CRC checks) where the individual elements
of the byte arrays were compared one by one and an error trace would
be output if the byte arrays were determined to be different.
This commit improves the
Enable channel 144 on 5GHz band since 802.11ac introduced it.
Signed-off-by: Peter Oh p...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath10k/mac.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath10k/mac.c
b/drivers/net/wireless/ath/ath10k/mac.c
index
Hi Arend,
Is it ok to update the wiphy band information after registration.
I believe this will cause issues.
In
brcmfmac the firmware is queried to obtain the supported channels.
However, it returns the channels for the current country set in
firmware. So after probe/registration iw
On 2015-03-18 20:41, Johannes Berg wrote:
+ * The driver is expected to release its own buffered frames and also call
+ * ieee80211_tx_dequeue() within that callback.
Perhaps that should read
The driver is expected to release its own buffered frames (if any) and
request the remaining
On 2015-03-18 21:07, Johannes Berg wrote:
On Wed, 2015-03-18 at 21:03 +0100, Felix Fietkau wrote:
On 2015-03-18 20:41, Johannes Berg wrote:
+ * The driver is expected to release its own buffered frames and also
call
+ * ieee80211_tx_dequeue() within that callback.
Perhaps that should
Arend van Spriel arend@... writes:
On 03/17/15 22:01, Jürgen Bausa wrote:
Thanks, that worked. Now I have firmware and nvram-file and the driver
seems
to load ok. At least I have an interface wlan0.
However, I am not able to connect.Network-manager just says interface is
being set
Hello,
I am working on a project where I need to be able to modify a wireless
adapter's firmware. I'm trying to use the TP-LINK TL-WN821N with the
8192cu driver and firmware on a Raspberry Pi 2. I am trying to be able to
quickly stop the transmission of packets then and just as quickly be able
On 03/18/2015 02:15 PM, Orozco wrote:
Hello,
I am working on a project where I need to be able to modify a wireless
adapter's firmware. I'm trying to use the TP-LINK TL-WN821N with the
8192cu driver and firmware on a Raspberry Pi 2. I am trying to be able to
quickly stop the transmission
Signed-off-by: Michael Braun michael-...@fami-braun.de
---
net/mac80211/cfg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c
index 74f509c..62007ca 100644
--- a/net/mac80211/cfg.c
+++ b/net/mac80211/cfg.c
@@ -2297,7 +2297,7 @@ int
From: Arik Nemtsov a...@wizery.com
Seems Broadcom TDLS peers (Nexus 5, Xperia Z3) refuse to allow TDLS
connection when channel-switching is supported but the regulatory
classes IE is missing from the setup request.
Add a chandef to reg-class translation function to cfg80211 and use it
to add the
On Tue, 17 Mar 2015, Joe Perches wrote:
On Tue, 2015-03-17 at 08:06 -0400, Nicholas Mc Guire wrote:
Converting milliseconds to jiffies by val * HZ / 1000 is technically
OK but msecs_to_jiffies(val) is the cleaner solution and handles all
corner cases correctly. This is a minor API
39 matches
Mail list logo
