Madwifi has default best effort queue "tuned" for throughout
and its parameters are different from mac80211 defaults when
qos (WME) is disabled.
You would have to dump qos settings for both systems before
comparing them. I guess the easiest way is to make sure QoS
is enabled and send video
Hi,
On Mon, 2017-01-30 at 21:04 -0500, Mel Stimmel wrote:
> I have a problem that recently arose with my Thinkpad model T61
> running Ubuntu 16.04 with the Intel Pro 4965 installed.
> This system was working just fine until sometime in Dec., when
> after one of the routine updates,
Iain Hunter writes:
> Enable AP support allmulticast for MDNS. It can be enabled by bringing up
>
> the interface with ip command with the argument allmulticast on
>
> Signed-off-by: Iain Hunter
The commit log looks now ok, except there's an unnecessare
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> OF allows not only specifying platform devices but also describing
> devices on standard buses like PCI or USB. This change will allow
> reading info from DT for bcma buses hosted on PCI cards.
>
> Signed-off-by: Rafał Miłecki
Stanislaw Gruszka wrote:
> When we restart system using sysrq RT3290 device do not initalize
> properly, hance always enable it via WLAN_FUN_CTRL register on
> probe.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=85461
> Reported-and-tested-by: Giedrius
Stanislaw Gruszka wrote:
> As reported by Felix:
>
> Though protected by an ifdef, introducing an usb symbol dependency in
> the rt2x00lib module is a major inconvenience for distributions that
> package kernel modules split into individual packages.
>
> Get rid of this
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This allows tracking device state and e.g. makes devm work as expected.
>
> Signed-off-by: Rafał Miłecki
> Cc: Stable
Patch applied to wireless-drivers-next.git, thanks.
a971df0b9d04
Arend Van Spriel wrote:
> The driver advertises support for WOWLAN_NETDETECT but did not specify
> maximum amount of netdetect match sets. This was no issue due to a bug
> in nl80211. As that has been fixed, brcmfmac also needs fixing.
>
> Reviewed-by: Hante
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This allows tracking device state and e.g. makes devm work as expected.
>
> Signed-off-by: Rafał Miłecki
> Cc: Stable
At this stage of the cycle I think 4.11 is more approriate for this
Luciano Coelho wrote:
> From: Sara Sharon
>
> For old firmwares the memory wasn't allocated, resulting in panic.
> Make it dynamically allocated as well. Allow any order of functions
> call.
>
> Fixes: eef187a7b8a1 ("iwlwifi: enlarge number of ucode
Stanislaw Gruszka wrote:
> clk_get() takes two arguments and might return ERR_PTR(), so we
> have to nullify pointer on that case, to do not break further call
> to clk_get_rate().
>
> Reported-by: Felix Fietkau
> Fixes: 34db70b92fae ("rt2x00: add copy of clk
Larry Finger wrote:
> From: Jurij Smakov
>
> In commit cf4747d7535a ("rtlwifi: Fix regression caused by commit
> d86e64768859, an error in the edit results in the wrong firmware
> being loaded for some models of the RTL8188/8192CE. In this condition,
Tony Lindgren writes:
> * Pavel Machek [170127 11:41]:
>> On Fri 2017-01-27 17:23:07, Kalle Valo wrote:
>> > Pali Rohár writes:
>> >
>> > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote:
>> > >> Pali Rohár
Larry Finger writes:
> From: Jurij Smakov
>
> In commit cf4747d7535a ("rtlwifi: Fix regression caused by commit
> d86e64768859, an error in the edit results in the wrong firmware
> being loaded for some models of the RTL8188/8192CE. In this condition,
I just noticed my DIR-885L has some weird NVRAM format. Linux doesn't
support it, it reads only part of it, which may affect brcmfmac.
There goes the most interesting part:
46 4c 53 48 50 3e 00 00 3f 01 00 00 4b 01 00 00 |FLSHP>..?...K...|
0010 00 00 00 00 31 3a 70 61 35 67 38
From: Tamizh chelvam
Rx filter reset and the dynamic tx switch mode (EXT_RESOURCE_CFG)
configuration are causing the following errors when UTF firmware
is loaded to the target.
Error message 1:
[ 598.015629] ath10k_pci 0001:01:00.0: failed to ping firmware: -110
[
I have a problem that recently arose with my Thinkpad model T61
running Ubuntu 16.04 with the Intel Pro 4965 installed.
This system was working just fine until sometime in Dec., when
after one of the routine updates, the software can't see/find/recognize
the wireless adapter. It's not
From: Jurij Smakov
In commit cf4747d7535a ("rtlwifi: Fix regression caused by commit
d86e64768859, an error in the edit results in the wrong firmware
being loaded for some models of the RTL8188/8192CE. In this condition,
the connection suffered from high ping latency, slow
From: Jurij Smakov
In commit cf4747d7535a ("rtlwifi: Fix regression caused by commit
d86e64768859, an error in the edit results in the wrong firmware
being loaded for some models of the RTL8188/8192CE. In this condition,
the connection suffered from high ping latency, slow
I noticed there is a new state "Needs Review / ACK" in patchwork.
I am going to use this for situations where I am explicitly waiting
either for a maintainer, or someone referenced directly in the patch
discussion, to review and ACK/NACK the change.
Just FYI...
From: Kalle Valo
Date: Sun, 29 Jan 2017 16:49:02 +0200
> small but important fixes for 4.10. Hopefully is the last pull request
> for 4.10.
>
> Please let me know if there are any problems.
Pulled, thanks Kalle.
Klaus Kinski writes:
> The captures I used to create the statistics are here:
> https://drive.google.com/open?id=0ByFGz3ZH6JcYMGp0a05lYzBPNzA
>
> An obvious difference is, that Madwifi sends 5 packets in a row
> without waiting for an ACK whereas ath9k/mac80211 always seems to
Larry Finger writes:
> In commit cf4747d7535a ("rtlwifi: Fix regression caused by commit
> d86e64768859, an error in the edit results in the wrong firmware
> being loaded for some models of the RTL8188/8192CE.
>
> Fixes: cf4747d7535a ("rtlwifi: Fix regression caused by
Kalle Valo wrote:
>>> Are you planning to update the MAINTAINERS file or should I?
>> It would be great if you could take care of that.
> Ok, I'll send a patch.
Thanks!
>> [1] https://wireless.wiki.kernel.org/en/users/Drivers/ath9k
> I updated that now.
I've applied similar changes to the
On Monday 30 January 2017 18:53:09 Tony Lindgren wrote:
> * Pavel Machek [170127 11:41]:
> > On Fri 2017-01-27 17:23:07, Kalle Valo wrote:
> > > Pali Rohár writes:
> > > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote:
> > > >> Pali Rohár
* Pavel Machek [170127 11:41]:
> On Fri 2017-01-27 17:23:07, Kalle Valo wrote:
> > Pali Rohár writes:
> >
> > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote:
> > >> Pali Rohár writes:
> > >>
> > >> > 2) It was already tested
In commit cf4747d7535a ("rtlwifi: Fix regression caused by commit
d86e64768859, an error in the edit results in the wrong firmware
being loaded for some models of the RTL8188/8192CE.
Fixes: cf4747d7535a ("rtlwifi: Fix regression caused by commit d86e64768859")
Signed-off-by: Jurij Smakov
On Mon, Jan 30, 2017 at 8:17 AM, Toke Høiland-Jørgensen wrote:
> Klaus Kinski writes:
>
>> Hello all,
>>
>> this is a blast from the past, but something that still bothers me.
>> I have two systems with Atheros/QCA cards:
>>
>> System
Klaus Kinski writes:
> Hello all,
>
> this is a blast from the past, but something that still bothers me.
> I have two systems with Atheros/QCA cards:
>
> System A:
> OS and driver: Linux 3.18.36 with last Madwifi/sample code from trunk
>
>
Hello all,
this is a blast from the past, but something that still bothers me.
I have two systems with Atheros/QCA cards:
System A:
OS and driver: Linux 3.18.36 with last Madwifi/sample code from trunk
WLAN card: AR5413 (Senao EMP-8602 PLUS-S)
System B:
OS and driver: Linux 3.18.36 with
From: Rafał Miłecki
It's important to inform user so he knows things went wrong. He may also
want to get memory dump for further debugging purposes.
Signed-off-by: Rafał Miłecki
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c | 12 ++--
From: Rafał Miłecki
This method may be unsupported (see: USB bus) or may just fail (see:
SDIO bus).
While at it rework logic in brcmf_sdio_bus_get_memdump function to avoid
too many conditional code nesting levels.
Signed-off-by: Rafał Miłecki
---
Enable AP support allmulticast for MDNS. It can be enabled by bringing up
the interface with ip command with the argument allmulticast on
Signed-off-by: Iain Hunter
---
drivers/net/wireless/ti/wlcore/main.c | 14 ++
1 file changed, 14 insertions(+)
diff --git
Iain Hunter writes:
> Let AP support allmulticast for MDNS.
> It can be enabled by bringing up the interface with ip command with the
> argument allmulticast on
>
> Signed-off-by: Iain Hunter
I see your patch now in patchwork (twice actually):
Let AP support allmulticast for MDNS.
It can be enabled by bringing up the interface with ip command and the argument
allmulticast on
Signed-off-by: Iain Hunter
---
drivers/net/wireless/ti/wlcore/main.c | 14 ++
1 file changed, 14 insertions(+)
diff --git
Let AP support allmulticast for MDNS.
It can be enabled by bringing up the interface with ip command with the
argument allmulticast on
Signed-off-by: Iain Hunter
---
drivers/net/wireless/ti/wlcore/main.c | 14 ++
1 file changed, 14 insertions(+)
diff --git
The "Indoor Use of low power wireless equipment in the frequency band 5
GHz (Exemption from Licensing Requirement) Rules, 2005" notification by
Ministry of Communications and Information Technology (Wireless Planning
and Coordination Wing) (New Delhi, the 28th January 2005) does not
mandate use of
On Mon, 2017-01-30 at 13:40 +0200, Kalle Valo wrote:
> Luca Coelho writes:
>
> > From: Sara Sharon
> >
> > For old firmwares the memory wasn't allocated, resulting in panic.
> > Make it dynamically allocated as well. Allow any order of functions
> > call.
Luca Coelho writes:
> From: Sara Sharon
>
> For old firmwares the memory wasn't allocated, resulting in panic.
> Make it dynamically allocated as well. Allow any order of functions
> call.
>
> Fixes: eef187a7b8a1 ("iwlwifi: enlarge number of ucode
When we restart system using sysrq RT3290 device do not initalize
properly, hance always enable it via WLAN_FUN_CTRL register on
probe.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=85461
Reported-and-tested-by: Giedrius Statkevičius
Signed-off-by:
From: Sara Sharon
For old firmwares the memory wasn't allocated, resulting in panic.
Make it dynamically allocated as well. Allow any order of functions
call.
Fixes: eef187a7b8a1 ("iwlwifi: enlarge number of ucode sections")
Signed-off-by: Sara Sharon
On Mon, Jan 30, 2017 at 02:15:58PM +0530, c_tr...@qti.qualcomm.com wrote:
> From: Tamizh chelvam
>
> Rx filter reset and the dynamic tx switch mode (EXT_RESOURCE_CFG)
> configuration are causing the following errors when UTF firmware
> is loaded to the target.
>
>
On Sun, Jan 29, 2017 at 04:53:38PM +0200, Kalle Valo wrote:
> Stanislaw Gruszka writes:
>
> > clk_get() takes two arguments and might return ERR_PTR(), so we
> > have to nullify pointer on that case, to do not break further call
> > to clk_get_rate().
> >
> > Reported-by:
From: Tamizh chelvam
Rx filter reset and the dynamic tx switch mode (EXT_RESOURCE_CFG)
configuration are causing the following errors when UTF firmware
is loaded to the target.
Error message 1:
[ 598.015629] ath10k_pci 0001:01:00.0: failed to ping firmware: -110
[
44 matches
Mail list logo