Re: Participation in common kernel API recommendation?

Arend Van Spriel writes: >> Would any members be interested in spending a one hour meeting with the >> subcommittee to give some feedback on the recommendation? If so, please >> let me know. > > Just throwing a wild idea at you. In the spirit of how the community >

Re: Cubieboard2 + hostapd + 100 wireless devices

Hi On Wed, May 10, 2017 at 04:30:35PM +0200, Marek Floriańczyk wrote: > I'm running hostapd in debug mode now, and I have found station: > 2c:3a:e8:00:33:e0 > That deauthenticate with AP, but I don't know why, > reason_code=3 "station is leaving (or has left) IBSS or ESS" Not sure about ESP

[PATCH] iwlegacy: warn when enabling power save

iwlegacy firmware can crash when power save is configured. PS was allowed in "dbdac2b iwlegacy: properly enable power saving" with belive that user who enable PS is aware of that and can relate firmware crahes with PS. However some distributions seems to enable PS without user intervention, so

[PATCH v2] iwlegacy: warn when enabling power save

iwlegacy firmware can crash when power save is configured. PS was allowed in "dbdac2b iwlegacy: properly enable power saving" with belive that user who enable PS is aware of that and can relate firmware crahes with PS. However some distributions seems to enable PS without user intervention, so

Re: [PATCH] iwlegacy: warn when enabling power save

On 5/15/2017 11:20 AM, Stanislaw Gruszka wrote: On Mon, May 15, 2017 at 11:41:05AM +0300, Kalle Valo wrote: Stanislaw Gruszka writes: iwlegacy firmware can crash when power save is configured. PS was allowed in "dbdac2b iwlegacy: properly enable power saving" with belive

Re: [PATCH] iwlegacy: warn when enabling power save

On Mon, May 15, 2017 at 11:25:51AM +0200, Arend van Spriel wrote: > On 5/15/2017 11:20 AM, Stanislaw Gruszka wrote: > >On Mon, May 15, 2017 at 11:41:05AM +0300, Kalle Valo wrote: > >>Stanislaw Gruszka writes: > >> > >>>iwlegacy firmware can crash when power save is

Re: [PATCH] iwlegacy: warn when enabling power save

Stanislaw Gruszka writes: > iwlegacy firmware can crash when power save is configured. PS was > allowed in "dbdac2b iwlegacy: properly enable power saving" with belive > that user who enable PS is aware of that and can relate firmware crahes > with PS. However some

Re: ath10k: controlling TX aggregation

On Fri, May 12, 2017 at 8:15 PM, Ben Greear wrote: > What chipset, and what firmware version? > > Thanks, > Ben Hi Ben, I have missed your response. PFB details. chip: QCA986x/988x PCIe FW ver: 10.2.4.70.54 api 5 kernel: 4.11.0-rc+7 (wireless-drivers-next) > On

Re: [PATCH] iwlegacy: warn when enabling power save

On Mon, May 15, 2017 at 11:41:05AM +0300, Kalle Valo wrote: > Stanislaw Gruszka writes: > > > iwlegacy firmware can crash when power save is configured. PS was > > allowed in "dbdac2b iwlegacy: properly enable power saving" with belive > > that user who enable PS is aware of

[PATCH v2 1/5] wil6210: low level RF sector API

From: Lior David Added vendor commands for low level control over RF sectors. It allows user space a fine-grained control over RF characteristics for TX and RX, such as direction and gain of TX/RX. Main usages are debugging and diagnostics, but also operational use

[PATCH v2 3/5] wil6210: Improve AP stop handling

From: Hamad Kadmany Set resetting flag early when stopping AP to avoid disconnect events as a result of disconnect command sent during AP stop procedure. Signed-off-by: Hamad Kadmany Signed-off-by: Maya Erez

[PATCH v2 2/5] wil6210: add option to load FTM FW

From: Hamad Kadmany Module parameter allows to load specific FW used for FTM testing. Signed-off-by: Hamad Kadmany Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/pcie_bus.c | 18

[PATCH v2 0/5] wil6210 patches

This set of patches include the following: - Fix for "low level RF sector API" patch - Addtotional wil6210 fixes Hamad Kadmany (2): wil6210: add option to load FTM FW wil6210: Improve AP stop handling Lior David (1): wil6210: low level RF sector API Maya Erez (2): wil6210: add option to

[PATCH v2 4/5] wil6210: add option to ignore OTA regulatory hints

On some platforms, the regulatory domain (country) is set using mechanisms external to WIFI, such as cellular modem and GPS. In these scenarios the regulatory hints that are received over the air (in beacons and similar) can conflict and even cause an incorrect country to be set. Add an option to

[PATCH v2 5/5] wil6210: support devices with different PCIe bar size

wil6210 devices can have different PCIe bar size, hence get the bar size from PCIe device instead of using a constant bar size. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/ioctl.c| 4 ++-- drivers/net/wireless/ath/wil6210/pcie_bus.c | 17

[PATCH] rt2x00: improve calling conventions for register accessors

With CONFIG_KASAN enabled and gcc-7, we get a warning about rather high stack usage (with a private patch set I have to turn on this warning, which I intend to get into the next kernel release): wireless/ralink/rt2x00/rt2800lib.c: In function 'rt2800_bw_filter_calibration':

Re: [PATCH] rt2x00: improve calling conventions for register accessors

On Mon, May 15, 2017 at 4:28 PM, Stanislaw Gruszka wrote: > On Mon, May 15, 2017 at 03:46:55PM +0200, Arnd Bergmann wrote: >> With CONFIG_KASAN enabled and gcc-7, we get a warning about rather high >> stack usage (with a private patch set I have to turn on this warning, >>

Re: [PATCH] rt2x00: improve calling conventions for register accessors

From: Stanislaw Gruszka Date: Mon, 15 May 2017 16:28:01 +0200 > On Mon, May 15, 2017 at 03:46:55PM +0200, Arnd Bergmann wrote: >> With CONFIG_KASAN enabled and gcc-7, we get a warning about rather high >> stack usage (with a private patch set I have to turn on this warning,

Re: [PATCH] rt2x00: improve calling conventions for register accessors

On Mon, May 15, 2017 at 10:40:52AM -0400, David Miller wrote: > From: Arnd Bergmann > Date: Mon, 15 May 2017 16:36:45 +0200 > > > On Mon, May 15, 2017 at 4:28 PM, Stanislaw Gruszka > > wrote: > >> On Mon, May 15, 2017 at 03:46:55PM +0200, Arnd Bergmann

BUG related to NAPI and ath10k in 4.9 + hacks kernel.

This is from a test system running my hacked 4.9 kernel, with 9888 ath10k NIC which often fails during startup. The firmware did fail to boot this time, and maybe it left things in a weird state. Then, the whole OS crashed with BUG. [ cut here ] kernel BUG at

[PATCH] libertas: Remove function entry/exit debugging

In at least one place, the enter/exit debugging was not being correctly matched. Based on mailing list feedback, it was desired to drop all of these in favor of using ftrace instead. Suggested-by: Joe Perches Suggested-by: Kalle Valo Signed-off-by: Kees

[PATCH 1/1] dt-binding: net: wireless: fix node name in the BCM43xx example

The example in the BCM43xx documentation uses "brcmf" as node name. However, wireless devices should be named "wifi" instead. Fix this to make sure that .dts authors can simply use the documentation as reference (or simply copy the node from the documentation and then adjust only the board

[PATCH 0/1] fix node name in the brcm,bcm43xx-fmac.txt example

recently there were some negative comments about the quality of code-reviews for new .dts additions. one issue that came up was that the node for the Broadcom FullMAC wireless SDIO devices was named "brcmf" instead of "wifi". This patch tries to fix (one of) the root cause(s), which is that .dts

Re: BUG related to NAPI and ath10k in 4.9 + hacks kernel.

On 05/15/2017 11:26 AM, Ben Greear wrote: This is from a test system running my hacked 4.9 kernel, with 9888 ath10k NIC which often fails during startup. The firmware did fail to boot this time, and maybe it left things in a weird state. Then, the whole OS crashed with BUG. I think the bug

[PATCH v3] libertas: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, redefine the stat strings to be ETH_GSTRING_LEN sizes, like other drivers. This lets us use a single memcpy that does not

Re: [PATCH] rt2x00: improve calling conventions for register accessors

On Mon, May 15, 2017 at 03:46:55PM +0200, Arnd Bergmann wrote: > With CONFIG_KASAN enabled and gcc-7, we get a warning about rather high > stack usage (with a private patch set I have to turn on this warning, > which I intend to get into the next kernel release): > >

Re: [PATCH] rt2x00: improve calling conventions for register accessors

From: Arnd Bergmann Date: Mon, 15 May 2017 16:36:45 +0200 > On Mon, May 15, 2017 at 4:28 PM, Stanislaw Gruszka > wrote: >> On Mon, May 15, 2017 at 03:46:55PM +0200, Arnd Bergmann wrote: >>> With CONFIG_KASAN enabled and gcc-7, we get a warning about rather

Re: [PATCH 1/1] dt-binding: net: wireless: fix node name in the BCM43xx example

On 15-5-2017 22:13, Martin Blumenstingl wrote: > The example in the BCM43xx documentation uses "brcmf" as node name. > However, wireless devices should be named "wifi" instead. Fix this to Hi Martin, Since when is that a rule. I never got the memo and the DTC did not ever complain to me about

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

On Fri, May 12, 2017 at 11:02:26PM +0200, Arend Van Spriel wrote: > try again.. replacing email address from Michał > On 12-5-2017 22:55, Arend Van Spriel wrote: > > Let me explain the idea to refresh your memory (and mine). It started > > when we were working on adding driver support for OpenWrt

Re: [PATCH] ath10k: fix out of bounds access to local buffer

Michael Mera writes: > Marcin Rokicki writes: >> Please send again to ath...@lists.infradead.org with cc >> linux-wireless@vger.kernel.org >> > > Sorry for the mistake. Resent as requested. > > Just for the record, I followed instructions at: >