Am 03.06.2016 um 19:26 schrieb bruce m beach:
> Hello All
>
> I am still working on cleaning up ath9k_htc firmware build tree for about 6
> months now ( and looks like I'll be doing this for all eternity**2 ) and am
> not clear myself what I'm looking for right now.
>
> I'm looking for some ki
Am 03.06.2016 um 19:26 schrieb bruce m beach:
> Hello All
>
> I am still working on cleaning up ath9k_htc firmware build tree for about 6
> months now ( and looks like I'll be doing this for all eternity**2 ) and am
> not clear myself what I'm looking for right now.
>
> I'm looking for some kind
Johannes Berg writes:
> I'd blissfully forgotten how totally crufty this API is ... oh well.
Yesterday there was a user on IRC having problems with wext (I didn't
even bother to investigate what exactly) which was immediately solved by
switching to nl80211. But he had no idea that wext was depri
gcc-6 reports the following error with -Werror=unused-const-variable.
drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error:
'b43_phyops_a' defined but not used
Per Michael Büsch: "All a-phy code is usused", so remove phy_a.c
completely. Move the remaining Type-G initialization code int
Per Michael Büsch: "All a-phy code is usused", so remove it all.
Signed-off-by: Guenter Roeck
---
v2: Added patch
drivers/net/wireless/broadcom/b43/main.c | 31 +---
drivers/net/wireless/broadcom/b43/wa.c | 283 +++
drivers/net/wireless/broadcom/b43/xmit.c | 17 +
Lennert, I am a user of your mwl8k driver through the OpenWRT
distribution. When working with certain WiFi devices I get errors in
the kernel logs and network connectivity errors on the wireless device.
The dmesg logs look like this:
[539374.394607] ieee80211 phy1: Added a new stream for (BSSID M
On 06/03/2016 02:35 PM, Michael Büsch wrote:
On Fri, 3 Jun 2016 14:32:46 -0700
Guenter Roeck wrote:
gcc-6 reports the following error with -Werror=unused-const-variable.
drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error:
'b43_phyops_a' defined but not used
Turns out a lot of c
I changed drivers/ssb/driver_gpio.c to better fit the coding style.
I changed unsigned to unsigned int
Two comments were changed to not end on a line with the text.
Signed-off-by: Hugh Sipiere
---
drivers/ssb/driver_gpio.c | 26 ++
1 file changed, 14 insertions(+), 12 del
From: "Vittorio Gambaletta (VittGam)"
This patch has been added to the 3.18 stable tree. If you have any
objections, please let us know.
===
[ Upstream commit 0f9edcdd88a993914fa1d1dc369b35dc503979db ]
The Wistron DNMA-92 and Compex WLM200NX have inverted LED polarity
(active high
gcc-6 reports the following error if -Werror=unused-const-variable
is enabled.
drivers/net/wireless/intel/iwlwifi/dvm/lib.c:210:21: error:
'iwlagn_loose_lookup' defined but not used
Signed-off-by: Guenter Roeck
---
drivers/net/wireless/intel/iwlwifi/dvm/lib.c | 17 -
1 f
From: "Vittorio Gambaletta (VittGam)"
This patch has been added to the 4.1 stable tree. If you have any
objections, please let us know.
===
[ Upstream commit cd84042ce9040ad038e958bc67a46fcfc015c736 ]
The LED can be active high instead of active low on some hardware.
Add the led_a
From: "Vittorio Gambaletta (VittGam)"
This patch has been added to the 4.1 stable tree. If you have any
objections, please let us know.
===
[ Upstream commit 0f9edcdd88a993914fa1d1dc369b35dc503979db ]
The Wistron DNMA-92 and Compex WLM200NX have inverted LED polarity
(active high i
On Fri, 3 Jun 2016 14:32:46 -0700
Guenter Roeck wrote:
> gcc-6 reports the following error with -Werror=unused-const-variable.
>
> drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error:
> 'b43_phyops_a' defined but not used
>
> Turns out a lot of code in this file is unused, so let's r
gcc-6 reports the following error with -Werror=unused-const-variable.
drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error:
'b43_phyops_a' defined but not used
Turns out a lot of code in this file is unused, so let's remove it.
Reported-by: Fengguang Wu [0-day test robot]
Signed-off-
From: Arend van Spriel
Update MAINTAINERS file because of organizational changes.
Reviewed-by: Hante Meuleman
Reviewed-by: Pieter-Paul Giesberts
Reviewed-by: Franky Lin
Signed-off-by: Arend van Spriel
---
MAINTAINERS | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
From: wrightf
The error message is given for something that is not an error here as
the drive strength configuration may not be applicable for specific
devices. Therefor the error message is rephrased and changed to a
debug message.
Signed-off-by: Wright Feng
[ar...@broadcom.com: rephrase commi
From: wrightf
When using nmap tool with FMAC, the nmap packets were be dropped by kernel
because the size was too short. The kernel message showed like
"nmap: packet size is too short (42 <= 50)". It is caused by the packet
length is shorter than ndev->hard_header_len. According to definition of
From: wrightf
The bus rx sequence is not in order because that control and event
frames always cause immediate send, but data frames may be held
for glomming in firmware side. It is not actually an error as the
packets are still processed even if the RX sequence is not in order.
Therefor the erro
From: Hante Meuleman
SKBs can come with a prioriy. Currently a priority of 0..7 is
assumed. But this assumption is incorrect. To fix this any
priority of 0 or higher then 7 will be adjusted by calling
cfg80211_classify8021d
Reviewed-by: Arend Van Spriel
Reviewed-by: Franky Lin
Reviewed-by: Pie
From: Hante Meuleman
This patch adds support for the new PCIE devices 43525 and 43465.
Reviewed-by: Arend Van Spriel
Reviewed-by: Franky (Zhenhui) Lin
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Hante Meuleman
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/broadcom/brcm8021
This patch series provides:
* update contact info in MAINTAINERS file.
* support for BCM43525 and BCM43465 PCIe devices.
* couple of smallish fixes in SDIO.
The patch series is intended for v4.8 and applies to the master
branch of the wireless-drivers-next repository.
Arend van Spriel (1):
Only hardcode the LED behavior if the SROM doesn't provide any for all
LEDs of the card. This avoids instantiating LED triggers for unconnected
LEDs, while (hopefully) keeping things working for old cards with a
blank SROM.
Signed-off-by: Lucas Stach
---
drivers/net/wireless/broadcom/b43/leds.c
On Fri, 3 Jun 2016 23:04:03 +0200
Lucas Stach wrote:
> Only hardcode the LED behavior if the SROM doesn't provide any for all
> LEDs of the card. This avoids instantiating LED triggers for unconnected
> LEDs, while (hopefully) keeping things working for old cards with a
> blank SROM.
>
> Signed
gcc-6 reports:
drivers/net/wireless/marvell/libertas_tf/main.c:30:19: error:
'lbtf_driver_version' defined but not used
with -Werror=unused-const-variable=.
Reported-by: Fengguang Wu [0-day test robot]
Signed-off-by: Guenter Roeck
---
drivers/net/wireless/marvell/libertas_tf/main.c |
Colin King writes:
> From: Colin Ian King
>
> path_b_ok is being assigned but immediately after path_a_ok is being
> compared to the value 0x03. This appears to be a typo on the
> variable name, compare path_b_ok instead.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/net/wireless/realtek/r
> diff --git a/net/wireless/wext-core.c b/net/wireless/wext-core.c
> index 6250b1c..50583fb 100644
> --- a/net/wireless/wext-core.c
> +++ b/net/wireless/wext-core.c
> @@ -958,8 +958,28 @@ static int wireless_process_ioctl(struct net
> *net, struct ifreq *ifr,
> return private(dev
> Reworked to not require the global variable renaming in ath9k.
>
> Signed-off-by: Toke Høiland-Jørgensen
Huh. I wonder why you did that? Is it really better to call the
ieee80211_txq a swq and call the ath9k hardware queue a txq? I
thought doing the renaming made for more readable and
Hello All
I am still working on cleaning up ath9k_htc firmware build tree for about 6
months now ( and looks like I'll be doing this for all eternity**2 ) and am
not clear myself what I'm looking for right now.
I'm looking for some kind of simple request in the ath9k_htc driver, through
the usb
On Fri, Jun 03, 2016 at 10:34:08AM -0400, John W. Linville wrote:
> On Fri, Jun 03, 2016 at 09:06:23AM +0200, Johannes Berg wrote:
> >
> > > http://www.filewatcher.com/_/?q=wireless-legacy.git, maybe ?
> > >
> >
> > Seems to work - both have the same branches:
> >
> > adm8211
This adds RX airtime to the airtime deficit used in the scheduler. This
is not a definite win, but I have only done very limited testing where
it has been included. Feel free to skip this patch when testing.
Signed-off-by: Toke Høiland-Jørgensen
---
drivers/net/wireless/ath/ath9k/recv.c | 51 +++
This patch set is my first pass at attempting to add an airtime fairness
enforcing scheduler to ath9k (for use in access point mode). For some
background on this approach and its possible benefits see this paper:
https://www.usenix.org/event/usenix04/tech/general/full_papers/tan/tan.pdf
This is st
This modifies the logic in ath_txq_schedule to account airtime consumed
by each station and uses a deficit-based scheduler derived from FQ-CoDel
to try to enforce airtime fairness. The deficit is decreased on TX
completion and the scheduler simply makes scheduling decisions based on
this.
Signed-o
This patch leaves the code for ath9k's internal per-node per-tid
queues in place and just modifies the driver to also pull from
the new mac80211 intermediate software queues, and implements
the .wake_tx_queue method, which will cause mac80211 to deliver
packets to be sent via the new intermediate q
Uses the ts->duration + retry-chain information to account for time
spent transmitting to a station. Calculates the RX airtime from the rate
and packet length. Hopefully these figures are not too inaccurate.
Signed-off-by: Toke Høiland-Jørgensen
---
drivers/net/wireless/ath/ath9k/ath9k.h |
From: Michal Kazior
Qdiscs are designed with no regard to 802.11
aggregation requirements and hand out
packet-by-packet with no guarantee they are
destined to the same tid. This does more bad than
good no matter how fairly a given qdisc may behave
on an ethernet interface.
Software queuing used
On 06/03/2016 09:33 AM, Valo, Kalle wrote:
Ben Greear writes:
Is it possible to upgrade CT firmware to 10.2 WMI/HTT interfaces?
That's a good idea. That shouldn't be too hard, right? I don't think HTT needs
any changes, but for WMI few commands and ids need to be changed.
I was thinking th
On 06/03/2016 09:28 AM, Rajkumar Manoharan wrote:
On 2016-06-03 21:37, Ben Greear wrote:
On 06/03/2016 08:55 AM, Rajkumar Manoharan wrote:
On 2016-06-03 21:18, Ben Greear wrote:
On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
Earlier qca9888 device was brought up using 10.1 firmware and the
Ben Greear writes:
>>> Is it possible to upgrade CT firmware to 10.2 WMI/HTT interfaces?
>>
>> That's a good idea. That shouldn't be too hard, right? I don't think HTT
>> needs
>> any changes, but for WMI few commands and ids need to be changed.
>
> I was thinking the 10.2 mgt-over-htt API would
On 2016-06-03 21:37, Ben Greear wrote:
On 06/03/2016 08:55 AM, Rajkumar Manoharan wrote:
On 2016-06-03 21:18, Ben Greear wrote:
On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
Earlier qca9888 device was brought up using 10.1 firmware and then
later all firmware fixes and new features are mig
On 06/03/2016 09:09 AM, Valo, Kalle wrote:
Rajkumar Manoharan writes:
On 2016-06-03 21:18, Ben Greear wrote:
On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
Earlier qca9888 device was brought up using 10.1 firmware and then
later all firmware fixes and new features are migrated to 10.2/10.
On 06/03/2016 08:52 AM, Valo, Kalle wrote:
Ben Greear writes:
On 06/02/2016 08:26 AM, Valo, Kalle wrote:
Ben Greear writes:
I found a lot of problems with this code as well, and the 5 patches
starting from the URL below fixed the issues for me.
They are stuck as 'NA' in patchwork, but I d
Rajkumar Manoharan writes:
> On 2016-06-03 21:18, Ben Greear wrote:
>> On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
>>> Earlier qca9888 device was brought up using 10.1 firmware and then
>>> later all firmware fixes and new features are migrated to 10.2/10.2.x
>>> firmware branch. As all of
On 06/03/2016 08:55 AM, Rajkumar Manoharan wrote:
On 2016-06-03 21:18, Ben Greear wrote:
On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
Earlier qca9888 device was brought up using 10.1 firmware and then
later all firmware fixes and new features are migrated to 10.2/10.2.x
firmware branch. As
On 2016-06-03 21:18, Ben Greear wrote:
On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
Earlier qca9888 device was brought up using 10.1 firmware and then
later all firmware fixes and new features are migrated to 10.2/10.2.x
firmware branch. As all of 10.1 funtionalities are supported in 10.2
b
Ben Greear writes:
> On 06/02/2016 08:26 AM, Valo, Kalle wrote:
>> Ben Greear writes:
>>
>>> I found a lot of problems with this code as well, and the 5 patches
>>> starting from the URL below fixed the issues for me.
>>>
>>> They are stuck as 'NA' in patchwork, but I don't know why.
>>>
>>> htt
On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
Earlier qca9888 device was brought up using 10.1 firmware and then
later all firmware fixes and new features are migrated to 10.2/10.2.x
firmware branch. As all of 10.1 funtionalities are supported in 10.2
based firmware, removing 10.1 firmware su
QCA988X hw implements a different cycle counter wraparound
behaviour when compared to QCA4019. To properly handle different
wraparound logic for these chipsets replace already available
bool hw_params member, has_shifted_cc_wraparound, with an
enum which could be extended to handle different wrapar
In QCA4019, cycle counter wraparound is not tied to rx
clear counter. Each counter would wraparound individually
and after wraparound the respective counter will be reset
to 0x7fff while other counter still running unaffected.
Define a new wraparound type for this behaviour and handle
it separa
Currently testmode events for 10.x firmware are processed from
10.1 wmi event processing. In order to remove 10.1 firmware support,
testmode events should be handled from 10.2 event processing.
Signed-off-by: Rajkumar Manoharan
---
drivers/net/wireless/ath/ath10k/wmi.c | 12
1 file
Earlier qca9888 device was brought up using 10.1 firmware and then
later all firmware fixes and new features are migrated to 10.2/10.2.x
firmware branch. As all of 10.1 funtionalities are supported in 10.2
based firmware, removing 10.1 firmware support for qca9888 device.
Signed-off-by: Rajkumar M
On Fri, Jun 03, 2016 at 09:06:23AM +0200, Johannes Berg wrote:
>
> > http://www.filewatcher.com/_/?q=wireless-legacy.git, maybe ?
> >
>
> Seems to work - both have the same branches:
>
> adm8211 72c942ed694e [PATCH] adm8211: fix build breakage
> from skb->mac.raw
> at76
On Thu, Jun 02, 2016 at 06:18:27PM -0700, Guenter Roeck wrote:
> On Thu, Jun 02, 2016 at 02:38:04PM -0400, John W. Linville wrote:
> > It has recently come to my attention that the old wireless-legacy.git
> > tree is no longer available on kernel.org. I honestly have no idea
> > what happened to i
Hi,
If a wireless driver uses "iw_handler_def.private_args" to populate
iwpriv command for private ioctls
but handlers for private ioctls(iw_handler) of iw_handler_def.private
is set to NULL like "atmel" and "airo" wireless drivers.
For those case, the IOCTLs from SIOCIWFIRSTPRIV to SIOCIWLASTPRI
Arend van Spriel wrote:
> From: Franky Lin
>
> A regression was introduced in commit 9c349892ccc9 ("brcmfmac: revise
> handling events in receive path") which moves eth_type_trans() call
> to brcmf_rx_frame(). Msgbuf layer doesn't use brcmf_rx_frame() but invokes
> brcmf_netif_rx() directly. In
Hi
Sorry for the conflict. We misunderstood from our kernel-patch related
conversation that it is you are reluctant to accept that. So we
attempted to accomplish the same through app-side modification. Any
way, sorry again.
However, we are again concentrating on our kernel side modification,
and
> http://www.filewatcher.com/_/?q=wireless-legacy.git, maybe ?
>
Seems to work - both have the same branches:
adm8211 72c942ed694e [PATCH] adm8211: fix build breakage from
skb->mac.raw
at76279f8592e428 cfg80211: keep track of supported
interface modes (
On Fri, Jun 3, 2016 at 2:02 AM, Belisko Marek wrote:
>
> Hi Krishna,
>
> On Thu, Jun 2, 2016 at 10:21 PM, Krishna Chaitanya
> wrote:
> > On Thu, Jun 2, 2016 at 7:34 PM, Belisko Marek
> > wrote:
> >>
> >> Hello,
> >>
> >> I'm using kernel 4.1 with option CONFIG_CFG80211_INTERNAL_REGDB
> >> enabl
57 matches
Mail list logo
