Jakub Kicinski writes:
> From: Jakub Kicinski
>
> Signed-off-by: Jakub Kicinski
No need to change anything now but in the future please avoid empty
commit logs. And at some point I'll start automatically rejecting
patches with empty commit logs so better get used to this already now.
--
Kall
On Sat, 2015-06-06 at 20:37 -0600, Gerrit Renker wrote:
> A problem has been found in recent kernels where multiple
> calls using SIOCGIWSTATS return the same, identical value.
Which "value"? I believe these return a number of different values. What
are the returned values? Are they perhaps just 0
Hi, Alexis Green
I just take a look back on the code before implementing the Proactive
PREQ for PREP. For the case of reply and forward (target_flags &
MP_F_RF), the previous metric used is the one which resolved from
mpath->metric.
Refer here:
https://github.com/o11s/open80211s/blob/o11s-0.4.2/
Hi Yaniv,
On Sun, Jun 7, 2015 at 9:30 AM, Machani, Yaniv wrote:
> Hi,
> As the configuration file is HW depended it should be created per platform,
> we have set this wiki page and script to help with initial setup :
> http://processors.wiki.ti.com/index.php/Open_Source_Wireless_Connectivity_wlco
Rafał Miłecki writes:
> It seems Broadcom released two devices with conflicting device id. There
> are for sure 14e4:4321 PCI devices with BCM4321 (N-PHY) chipset, they
> can be found in routers, e.g. Netgear WNR834Bv2. However, according to
> Broadcom public sources 0x4321 is also used for 5 GHz
> From: Julia Lawall
>
> Delete jump to a label on the next line, when that label is not
> used elsewhere.
>
> A simplified version of the semantic patch that makes this change is as
> follows: (http://coccinelle.lip6.fr/)
>
> //
> @r@
> identifier l;
> @@
>
> -if (...) goto l;
> -l:
> //
>
> AR93xx and newer needs to stop rx before tx to avoid getting the DMA
> engine or MAC into a stuck state.
> This should reduce/fix the occurence of "Failed to stop Tx DMA" logspam.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Felix Fietkau
Thanks, applied to wireless-drivers-next.git.
Kall
Thanks. These look nice.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> This patch adds more detailed information about association failures
> - reason and states.
>
> Signed-off-by: Avinash Patil
> Signed-off-by: Cathy Luo
Thanks, 17 patches applied to wireless-drivers-next.git:
12d111097428 mwifiex: verbose logging for association failure messages
c951a66713
> After physical reconnect, the rtl8192cu chipset shows low
> transmission rates.It cause is that variable "iqk_initialized"
> do not de-initialized. So I add this code.
>
> Signed-off-by: Taehee Yoo
> Acked-by: Larry Finger
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsub
> From: Zhaoyang Liu
>
> This patch fixes semantic warning for debugging data dump feature.
> Previous code is based on the assumption that skb is not null.
> New change makes sure that we already have data buffer.
>
> Reported-by: Dan Carpenter
> Signed-off-by: Zhaoyang Liu
> Signed-off-by:
As mentioned in Section 13.10.9.3 Case E2, the PREQ forwarding should
use metric "as received + own metric toward transmitter of received
PREQ". So you are right.
Just MP_F_RF bit is no longer use. After replying with PREP,
forwarding the PREQ by setting the IEEE80211_PREQ_TO_FLAG in the per
targe
Hi,
I want to inject particular data into beacon frame in Android device.
I found two approaches:
1. Write loadable kernel module.
2. Modify MAC80211 subsystem
In the first approach, I found that I could not include directly
source code from MAC80211 sub system in folder /net/mac80211/. Thus, I
us
On Sat, 2015-06-06 at 19:10 -0400, Toan Pham wrote:
> I am experiencing a similar issue on another system (at91sam9n12) that
> uses Redpine Signal Wireless Driver 1.1.0. I do not know the root
> cause yet, but it may be related to the Redpine Signals driver. Will
> update this mailing list if th
Found during code review. This was pretty much
impossible to happen but better safe than sorry.
Signed-off-by: Michal Kazior
---
drivers/net/wireless/ath/ath10k/wmi-tlv.c | 3 ++-
drivers/net/wireless/ath/ath10k/wmi.c | 8 +---
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git
Rafał Miłecki writes:
> Recently Broadcom added support for NVRAMs with entries for multiple
> PCIe devices. One of the supported formats is based on prefixes defined
> like: devpath0=pcie/1/4/ and entries like 0:foo=bar 0:baz=qux etc.
>
> Unfortunately there are also a bit older devices using di
Rafał Miłecki writes:
> This allows e.g. user space to use /sys/class/ieee80211/*/macaddress
>
> Signed-off-by: Rafał Miłecki
Thanks, applied manually.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.
Jakub Kicinski writes:
> From: Jakub Kicinski
>
> Signed-off-by: Jakub Kicinski
Thanks, applied all four manually.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://v
Rafał Miłecki writes:
> As we plan to add support for platform NVRAM we should store direct
> data pointer without the extra struct firmware layer. This will allow
> us to support other sources with the only requirement being u8 buffer.
>
> Signed-off-by: Rafał Miłecki
> Acked-by: Arend van Spri
Rafał Miłecki writes:
> It seems Broadcom released two devices with conflicting device id. There
> are for sure 14e4:4321 PCI devices with BCM4321 (N-PHY) chipset, they
> can be found in routers, e.g. Netgear WNR834Bv2. However, according to
> Broadcom public sources 0x4321 is also used for 5 GHz
Rafał Miłecki writes:
> Signed-off-by: Rafał Miłecki
Thanks, both applied manually.
And in the future please avoid empty commit logs.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordom
This should help when analysing problems from
users and spot fw api blob problems easier.
Signed-off-by: Michal Kazior
---
drivers/net/wireless/ath/ath10k/core.c | 45 +
drivers/net/wireless/ath/ath10k/core.h | 3 +++
drivers/net/wireless/ath/ath10k/debug.c |
HTT version itself isn't sufficient to know what
HTT version given firmware blob uses. Hence print
the recently introduced HTT op version code.
While at it make the info string a bit more
consistent and clear.
Signed-off-by: Michal Kazior
---
drivers/net/wireless/ath/ath10k/debug.c | 3 ++-
1 f
From: Hante Meuleman
On device to host data using msgbuf the read pointer gets updated
once all data is processed. Updating this pointer more frequently
allows the firmware to add more data quicker. This will result in
slightly higher and more stable throughput on CPU bounded host
processors.
Re
The information provided by chipinfo is also provided by the
revinfo debugfs entry. Removing it from debugfs.
Reviewed-by: Hante Meuleman
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/brcm80211/brcmfmac/debug.c | 10 --
1 file changed, 10 d
Summary of this series:
* fix module reload issue for PCIe.
* improving msgbuf protocol for PCIe devices.
* cleanup of the debugfs code.
This series is intended for v4.2 kernel and applies to the master
branch of the wireless-drivers-next repository.
Arend van Spriel (3):
brcmfmac: remove chip
Some time ago the function debugfs_create_devm_seqfile() was
introduced in debugfs. The caller simply needs to provide a
device pointer and read function. The function brcmf_debugfs_add_entry()
is now simply a wrapper only doing the work for CONFIG_BRCMDBG.
Reviewed-by: Hante Meuleman
Reviewed-by
The watchdog reset as done in brcmf_pcie_buscoreprep() is not
sufficient. It needs to modify PCIe core registers as well
which is properly done by brcmf_pcie_reset_device() after the
chip recognition is done. So the faulty watchdog reset can be
removed as it was causing driver reload to fail and ha
On 06/08/15 14:35, Jörg Krause wrote:
Hi,
I've trouble creating the p2p interface on a BCM43362 wifi device
running Linux kernel 4.0.4:
# dmesg | grep brcmfmac
[7.010870] brcmfmac: brcmf_c_preinit_dcmds: Firmware version =
wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID
Janusz Dziedzic writes:
> Enable VHT support for IBSS.
>
> Signed-off-by: Janusz Dziedzic
You should give background info here. For example, why did you enable
now and not earlier? How did you test it? What user space requirements
(wpasupplicant version etc) there are? What kind of throughput d
Hi,
I've trouble creating the p2p interface on a BCM43362 wifi device
running Linux kernel 4.0.4:
# dmesg | grep brcmfmac
[7.010870] brcmfmac: brcmf_c_preinit_dcmds: Firmware version =
wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d
[7.158905] brcmfmac: br
"Li, Yanbo" writes:
>> -Original Message-
>> From: Valo, Kalle
>> Sent: Wednesday, May 27, 2015 5:57 AM
>> To: Li, Yanbo
>> Cc: dreamfly...@gmail.com; linux-wireless@vger.kernel.org;
>> michal.kaz...@tieto.com; ath...@lists.infradead.org
>> Subject: Re: [PATCH] ath10k: Debugfs entry to en
Hi Arend,
On Mo, 2015-06-08 at 14:41 +0200, Arend van Spriel wrote:
> On 06/08/15 14:35, Jörg Krause wrote:
> > Hi,
> >
> > I've trouble creating the p2p interface on a BCM43362 wifi device
> > running Linux kernel 4.0.4:
> >
> > # dmesg | grep brcmfmac
> > [7.010870] brcmfmac: brc
Hi,
by the looks of it Linus will release 4.1 on June 21st. So anything
which should go to 4.2 should be submitted to the list by Thursday June
11th. Anything later than that might need to wait for 4.3.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
Hi Arend,
On Mo, 2015-06-08 at 14:41 +0200, Arend van Spriel wrote:
> On 06/08/15 14:35, Jörg Krause wrote:
> > Hi,
> >
> > I've trouble creating the p2p interface on a BCM43362 wifi device
> > running Linux kernel 4.0.4:
> >
> > # dmesg | grep brcmfmac
> > [7.010870] brcmfmac: brc
Liu CF/TW writes:
> This change supports bypassing HW crypto engine by enabling raw Rx/Tx mode.
> This will enable use cases such as sw crypto and raw tx injection.
> This change introduces a new module param 'cryptmode'.
>
> cryptmode:
>
> 0Use HW crypto engine. Use native WiFi mode Tx/Rx e
Liu CF/TW writes:
> This change supports bypassing HW crypto engine by enabling raw Rx/Tx mode.
> This will enable use cases such as sw crypto and raw tx injection.
> This change introduces a new module param 'cryptmode'.
Please use full words, eg. sw -> software, hw -> hardware
> cryptmode:
>
Hi all,
I'm trying to figure out how to get rate control working in TX99.
Currently it's forced in code to rate = &tx_info->control.rates[0];
Every time I force/try anything besides "0" (which is the value of
tx_info->control.rates[0]) the module won't start radiating.
Can anyone provide any hel
On 06/08/15 15:48, Jörg Krause wrote:
Hi Arend,
On Mo, 2015-06-08 at 14:41 +0200, Arend van Spriel wrote:
On 06/08/15 14:35, Jörg Krause wrote:
Hi,
I've trouble creating the p2p interface on a BCM43362 wifi device
running Linux kernel 4.0.4:
# dmesg | grep brcmfmac
[7.010870]
You should build mac80211 as module instead of built-in driver and
"make modules" instead of full make. This way you'll be just
rebuilding mac80211.ko instead of the whole thing.
On Mon, Jun 8, 2015 at 2:39 AM, Duy Tai Nguyen wrote:
> Hi,
>
> I want to inject particular data into beacon frame in
I took a look at the spec too and also didn't see mention of the MP_F_RF
flag. Section 13.10.9.3 for example talks about PREQ handling and in case E2
talks about sending replies back. It says to do that if target only is not
set which makes sense: MP_F_RF and MP_F_DO are exclusive options so it's
s
Hi Kalle,
On Mon, 8 Jun 2015, Kalle Valo wrote:
For staging patches please prefix the title "staging: "
Here's a tip how you can check what commit title you should use:
git log --oneline drivers/staging/rtl8723au/include/rtw_io.h
Thanks a lot!
Xavier
--
To unsubscribe from this list: send the
On Mon, Jun 8, 2015 at 10:40 PM, Alexis Green wrote:
>
> You should build mac80211 as module instead of built-in driver and
> "make modules" instead of full make. This way you'll be just
> rebuilding mac80211.ko instead of the whole thing.
>
> On Mon, Jun 8, 2015 at 2:39 AM, Duy Tai Nguyen wrote:
On Tue, Jun 02, 2015 at 12:55:06PM +0400, Stanislav Kholmanskikh wrote:
> Fixed several syntax/style issues found with checkpatch.pl.
What exactly is "several"? Please be specific as to what type of
changes you are making.
Please fix and resend both of these.
thanks,
greg k-h
--
To unsubscribe
On Mon, May 18, 2015 at 5:45 PM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> Systems that have module signing currently enabled may
> wish to extend vetting of firmware passed to the kernel
> as well. We can re-use most of the code for module signing
> for firmware signature verifica
Aligned enum members to follow a common style per enum.
Signed-off-by: Stanislav Kholmanskikh
---
drivers/staging/wilc1000/coreconfigurator.c | 29 +++---
drivers/staging/wilc1000/coreconfigurator.h | 62 ++---
2 files changed, 46 insertions(+), 45 deletions(-)
d
Fixed the following issues found with checkpatch.pl:
* Multiple debug strings contained " \n". Changed
it to "\n".
* Changed 'return(X)' to 'return X'.
* Aligned TAG_PARAM_OFFSET to fit 80 columns
Signed-off-by: Stanislav Kholmanskikh
---
Changes since v3:
* Put a more detailed explanation
On Mon, Jun 08, 2015 at 12:41:08PM -0700, Greg KH wrote:
> On Tue, Jun 02, 2015 at 12:55:06PM +0400, Stanislav Kholmanskikh wrote:
> > Fixed several syntax/style issues found with checkpatch.pl.
>
> What exactly is "several"? Please be specific as to what type of
> changes you are making.
>
> Pl
On 06/08/15 22:17, Jörg Krause wrote:
On Mo, 2015-06-08 at 18:46 +0200, Arend van Spriel wrote:
On 06/08/15 15:48, Jörg Krause wrote:
Hi Arend,
On Mo, 2015-06-08 at 14:41 +0200, Arend van Spriel wrote:
On 06/08/15 14:35, Jörg Krause wrote:
Hi,
I've trouble creating the p2p interface on a BC
On Mo, 2015-06-08 at 18:46 +0200, Arend van Spriel wrote:
> On 06/08/15 15:48, Jörg Krause wrote:
> > Hi Arend,
> >
> > On Mo, 2015-06-08 at 14:41 +0200, Arend van Spriel wrote:
> > > On 06/08/15 14:35, Jörg Krause wrote:
> > > > Hi,
> > > >
> > > > I've trouble creating the p2p interface on a BC
Hi Msanari,
On Fri, Jun 05, 2015 at 09:38:19PM +0900, Masanari Iida wrote:
> This patch fix a spelling typo in nfc-hci.txt
>
> Signed-off-by: Masanari Iida
> ---
> Documentation/nfc/nfc-hci.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
Cheers,
Samuel.
--
To unsub
Is there any publicly available firmware binary that supports this feature,
even if one has to force the feature flag?
Thanks,
Ben
On 06/04/2015 03:11 PM, Ben Greear wrote:
> Is there any way to make this work on a 10.1 firmware, even if that means
> manually poking registers through debugfs?
>
Hi Valentin,
On Tue, Apr 28, 2015 at 11:08:47AM +0200, Valentin Rothberg wrote:
> The CPP identifier 'DEBUG' is not used in the source code of nfc at all,
> so we can safely remove setting it in both Makefiles.
>
> Signed-off-by: Valentin Rothberg
> ---
> I detected this issue with ./scripts/che
Hi Tomas,
On Thu, May 07, 2015 at 04:38:30PM +0300, Tomas Winkler wrote:
> In microread_i2c_irq_thread_fn 'client' set but not used
>
> Cc: Lauro Ramos Venancio
> Cc: Aloisio Almeida Jr
> Signed-off-by: Tomas Winkler
> ---
> drivers/nfc/microread/i2c.c | 3 ---
> 1 file changed, 3 deletions(-
Hi Uwe,
On Tue, May 19, 2015 at 09:22:56AM +0200, Uwe Kleine-König wrote:
> Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
> which appeared in v3.17-rc1, the gpiod_get* functions take an additional
> parameter that allows to specify direction and initial value for output.
Hi Joe,
On Sun, May 31, 2015 at 05:44:45PM -0700, Joe Perches wrote:
> Several of these goto exit; uses should be direct returns
> as skb is not yet initialized by nci_hci_get_param().
>
> Miscellanea:
>
> o Use !memcmp instead of memcmp() == 0
> o Remove unnecessary goto from if () {... goto ex
On Mo, 2015-06-08 at 23:14 +0200, Arend van Spriel wrote:
> On 06/08/15 22:17, Jörg Krause wrote:
> > On Mo, 2015-06-08 at 18:46 +0200, Arend van Spriel wrote:
> > > On 06/08/15 15:48, Jörg Krause wrote:
> > > > Hi Arend,
> > > >
> > > > On Mo, 2015-06-08 at 14:41 +0200, Arend van Spriel wrote:
>
This change supports hardware crypto engine bypass by enabling raw
Rx/Tx encap mode. This enables use cases such as software crypto and raw
tx injection. This change introduces a new module param 'cryptmode'.
cryptmode:
0: Use hardware crypto engine globally with native Wi-Fi mode TX/RX
en
> On Sat, 2015-06-06 at 20:37 -0600, Gerrit Renker wrote:
> > A problem has been found in recent kernels where multiple
> > calls using SIOCGIWSTATS return the same, identical value.
>
> Which "value"? I believe these return a number of different values. What
> are the returned values? Are they
The csa counter has moved from sdata to beacon/presp but
it is not updated accordingly for mesh and ibss. Fix this.
This regression is introduced by the following patch:
mac80211: move csa counters from sdata to beacon/presp
Signed-off-by: Chun-Yeow Yeoh
---
net/mac80211/cfg.c | 1 +
net/mac80
60 matches
Mail list logo
