Dear Arend,
as followup to my last inquiry, since it's passed more than 2 weeks, I'm
afraid I didn't receive any answer.
As from subject, I finally discovered that brcmsmac is not compliant to
802.11 regulations for BCM4313.
So, as purchasing customer, and member of Linux users community, I try
to
(I don't know why I've been added on this e-mail chain, I'm not in any
way linked to broadcom or any of their drivers)
On 03/04/2015 09:39 AM, Nikita N. wrote:
Dear Arend,
as followup to my last inquiry, since it's passed more than 2 weeks, I'm
afraid I didn't receive any answer.
As from
On Wed, Mar 4, 2015 at 12:38 PM, Marek Puzyniak
marek.puzyn...@tieto.com wrote:
On 4 March 2015 at 11:04, Arik Nemtsov a...@wizery.com wrote:
I can do it, but I'll probably only get to it next week.
I will try to prepare patch this week, if not I will wait for Arik's
proposition.
For ath10k
Some variables in structs iwl_mvm and iwl_mvm_vif are used for debug
purpose, and are declared only if CONFIG_IWLWIFI_DEBUGFS is
set. However, some of these variables are used even if
CONFIG_IWLWIFI_DEBUGFS is not set, resulting in a compilation error.
This patch aims to fix this issue by adding a
From: Mike Frysinger vap...@chromium.org
Rather than append -O2 -g all the time to the user's CFLAGS (and thus
clobbering whatever they have set up), initialize the default value to
that and let the user override it entirely.
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
Makefile | 4 ++--
From: Mike Frysinger vap...@chromium.org
Forcing -Werror at build time easily breaks across compiler settings,
compiler versions, architectures, C libraries, etc... Add a knob so
distro peeps can turn it off.
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
Makefile | 3 ++-
1 file changed,
Hi,
On Wed, 2015-03-04 at 18:59 +0100, Alban Gruin wrote:
Some variables in structs iwl_mvm and iwl_mvm_vif are used for debug
purpose, and are declared only if CONFIG_IWLWIFI_DEBUGFS is
set. However, some of these variables are used even if
CONFIG_IWLWIFI_DEBUGFS is not set, resulting in a
On Wed, 2015-03-04 at 18:30 +0200, Arik Nemtsov wrote:
On Wed, Mar 4, 2015 at 12:38 PM, Marek Puzyniak
marek.puzyn...@tieto.com wrote:
On 4 March 2015 at 11:04, Arik Nemtsov a...@wizery.com wrote:
I can do it, but I'll probably only get to it next week.
I will try to prepare patch this
From: Mike Frysinger vap...@chromium.org
This file uses BN_ULONG but doesn't include the openssl headers leading
to build failures:
keys-ssl.c:2:8: error: unknown type name 'BN_ULONG'
static BN_ULONG e_0[1] = {
The large unqualified constants also break building:
keys-ssl.c:8:2: warning:
From: Mike Frysinger vap...@chromium.org
Let the distro/user deal with ldconfig updating. Running it blindly like
this breaks DESTDIR installs as `ldconfig` only operates on system paths.
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
Makefile | 1 -
1 file changed, 1 deletion(-)
diff
On Wed, 2015-03-04 at 14:51 -0500, Mike Frysinger wrote:
From: Mike Frysinger vap...@chromium.org
Forcing -Werror at build time easily breaks across compiler settings,
compiler versions, architectures, C libraries, etc... Add a knob so
distro peeps can turn it off.
+WERROR = -Werror
On Wed, 2015-03-04 at 15:22 -0500, Mike Frysinger wrote:
yes, if you wanted to support:
WERROR= make
but the expectation is that you'd do:
make WERROR=
in which case this code is working as i intended.
Oh, interesting, I wasn't even really aware of this difference :)
Heh.
/linux/kernel/git/kvalo/wireless-drivers-next.git/commit/?id=2264fc857decd45798368f46861d9aecac23546f
However, that commit is in next-20150304 and we still get the error
(see, for example,
http://kisskb.ellerman.id.au/kisskb/buildresult/12376688/).
We're working on this, see
http://marc.info/?t
=2264fc857decd45798368f46861d9aecac23546f
However, that commit is in next-20150304 and we still get the error
(see, for example,
http://kisskb.ellerman.id.au/kisskb/buildresult/12376688/).
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgptkI9Uoc1PO.pgp
Description: OpenPGP digital
On 04 Mar 2015 20:53, Johannes Berg wrote:
On Wed, 2015-03-04 at 14:51 -0500, Mike Frysinger wrote:
From: Mike Frysinger vap...@chromium.org
Forcing -Werror at build time easily breaks across compiler settings,
compiler versions, architectures, C libraries, etc... Add a knob so
distro
On 04 Mar 2015 21:31, Johannes Berg wrote:
On Wed, 2015-03-04 at 15:22 -0500, Mike Frysinger wrote:
yes, if you wanted to support:
WERROR= make
but the expectation is that you'd do:
make WERROR=
in which case this code is working as i intended.
Oh, interesting, I wasn't
Driver for PCIe core requires PCI to be enabled, however we shouldn't
require it for the whole bus. Someone may be not interested in extra
PCI devices and what's more there are SoCs without any PCI at all (like
BCM5356C0, BCM5357*, BCM47186B0). For more details see Kconfig help.
Please note this
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function
Hi Kalle,
-Original Message-
From: Kalle Valo [mailto:kv...@codeaurora.org]
Sent: Tuesday, March 03, 2015 6:08 PM
To: Avinash Patil
Cc: linux-wireless@vger.kernel.org; Amitkumar Karwar; Cathy Luo; Zhaoyang Liu;
Shengzhen Li; Marc Yang
Subject: Re: [PATCH 1/4] mwifiex: avoid
carl1970: monitor mode only displaying beacons/probs from APs
Hello,
Quite a while back after doing an upgrade to the latest (back then)
compat-wireless, I noticed that I was only seeing beacon,prob requests, and
the occasional data packet when in monitor mode; which at the time I wrote
off.
On Tue, 2015-03-03 at 12:07 +0200, Arik Nemtsov wrote:
And doing so would also address the nss problem, right? IIRC that's done
in the rate control init inline.
Right.
Can one of you (Marek/Arik) send a combined patch then please? :)
johannes
--
To unsubscribe from this list: send the
On Tue, 2015-03-03 at 17:53 +0530, Rajkumar Manoharan wrote:
@@ -696,6 +698,7 @@ struct cfg80211_ap_settings {
u8 p2p_ctwindow;
bool p2p_opp_ps;
const struct cfg80211_acl_data *acl;
+ int low_ack_threshold;
should probably be unsigned?
};
/**
diff --git
On Tue, 2015-03-03 at 17:53 +0530, Rajkumar Manoharan wrote:
Store the low ack threshold configured by user in BSS config.
This will be used by driver for triggering low ack event whenever
the station is not ACKing the number of frames mentioned in
threshold.
Err, this cannot possibly be
On Sun, 2015-03-01 at 09:10 +0200, Emmanuel Grumbach wrote:
From: Avri Altman avri.alt...@intel.com
Allow drivers to obtain the user's TX power restrictions in
order to be able to apply it properly on (for example)
hardware scanning which operations on a set of channels,
in which case
On Wed, Mar 4, 2015 at 10:16 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Tue, 2015-03-03 at 12:07 +0200, Arik Nemtsov wrote:
And doing so would also address the nss problem, right? IIRC that's done
in the rate control init inline.
Right.
Can one of you (Marek/Arik) send a
On 4 March 2015 at 11:04, Arik Nemtsov a...@wizery.com wrote:
I can do it, but I'll probably only get to it next week.
I will try to prepare patch this week, if not I will wait for Arik's
proposition.
For ath10k rate control need to be initialised before moving to
STA_AUTHORIZED, so
Marek Puzyniak marek.puzyn...@tieto.com writes:
During wmm tests changing wmm parameters did not change anything.
This was because of mismatch in WMM params per vdev command.
WMM params per vdev uses different command structure than wmm params
per pdev command.
Patch concerns qca6174.
We were providing declarations but actual code was compiled only with
CONFIG_BCMA_HOST_PCI set. This could result in:
ERROR: bcma_host_pci_down
[drivers/net/wireless/brcm80211/brcmsmac/brcmsmac.ko] undefined!
ERROR: bcma_host_pci_up [drivers/net/wireless/brcm80211/brcmsmac/brcmsmac.ko]
Previously, the indoor setting configuration assumed that as
long as a station interface is connected, the indoor environment
setting does not change. However, this assumption is problematic
as:
- It is possible that a station interface is connected to a mobile
AP, e.g., softAP or a P2P GO,
Timeout was scheduled only in case CRDA was called due to user hints,
but was not scheduled for other cases. This can result in regulatory
hint processing getting stuck in case that there is no CRDA configured.
Change this by scheduling a timeout every time CRDA is called. In
addition, in
Directly update the indoor setting without wrapping it as
a regulatory request, to simplify the processing.
Signed-off-by: Ilan Peer ilan.p...@intel.com
---
net/wireless/reg.c | 34 +++---
1 file changed, 3 insertions(+), 31 deletions(-)
diff --git
SF Markus Elfring elfr...@users.sourceforge.net writes:
From: Markus Elfring elfr...@users.sourceforge.net
Date: Wed, 4 Feb 2015 19:30:23 +0100
The release_firmware() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This
-Original Message-
From: Luis R. Rodriguez [mailto:mcg...@suse.com]
Sent: Monday, March 02, 2015 23:23
To: Peer, Ilan
Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov
Subject: Re: [PATCH v9 2/3] cfg80211: Add API to change the indoor
regulatory setting
On Sun, Mar 01, 2015 at
On 4 March 2015 at 07:19, Rafał Miłecki zaj...@gmail.com wrote:
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M]
Michal Kazior michal.kaz...@tieto.com writes:
qca6174 WLAN.RM.2.0-00073 firmware uses full rx
reordering offload and delivers Rx via a new HTT
event. The event however is incorrectly generated
in firmware and becomes overly long (with trailing
garbage). This was hitting defined CE buffer
Jim Davis jim.ep...@gmail.com writes:
Building with the attached random configuration file,
drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
drivers/bcma/driver_pcie2.c:196:2: error: implicit declaration of
function 'pcie_set_readrq' [-Werror=implicit-function-declaration]
On 4 March 2015 at 13:08, Rafał Miłecki zaj...@gmail.com wrote:
On 4 March 2015 at 07:19, Rafał Miłecki zaj...@gmail.com wrote:
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building
Michal Kazior michal.kaz...@tieto.com writes:
qca6184 WLAN.RM.2.0-00073 has a bug in sta
powersave state machine and requires peer param to
be poked to enable the powersave.
Calling this unconditionally should be safe for
other chips/firmwares.
Signed-off-by: Michal Kazior
These functions are not exported nor used anywhere, so there is no
reason to put them in public headers.
Also drop unused bcma_chipco_(suspend|resume).
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
I hope my logic is OK about that?
---
drivers/bcma/bcma_private.h | 41
Johannes Berg johan...@sipsolutions.net writes:
+Arik.
It'd be nice (for me anyway) if you didn't send this in a series of
other patches I don't care about - I only ever saw this due to
patchwork.
Yes, mac80211 and driver patches need to be sent in separate series. I
will drop this series
40 matches
Mail list logo
