Re: [PATCH] nl80211: Fix unfiltered GET_INTERFACE dumps

On 25-08-16 22:44, Denis Kenzior wrote: > dump_wiphy_parse only assigns filter_wiphy if one of the supported > NL80211 attributes is present. So for unfiltered dumps, filter_wiphy > was always initialized to 0, and only interface 0 was dumped. > > This was introduced in commit

Re: [PATCH] nl80211: Fix unfiltered GET_INTERFACE dumps

On 25-08-16 23:52, Denis Kenzior wrote: > Hi Arend, > > On 08/25/2016 04:35 PM, Arend van Spriel wrote: >> On 25-08-16 22:44, Denis Kenzior wrote: >>> dump_wiphy_parse only assigns filter_wiphy if one of the supported >>> NL80211 attributes is present. So for unfiltered dumps, filter_wiphy >>>

Re: [PATCH] nl80211: Fix unfiltered GET_INTERFACE dumps

Hi Arend, On 08/25/2016 04:35 PM, Arend van Spriel wrote: On 25-08-16 22:44, Denis Kenzior wrote: dump_wiphy_parse only assigns filter_wiphy if one of the supported NL80211 attributes is present. So for unfiltered dumps, filter_wiphy was always initialized to 0, and only interface 0 was

[PATCH] nl80211: Fix unfiltered GET_INTERFACE dumps

dump_wiphy_parse only assigns filter_wiphy if one of the supported NL80211 attributes is present. So for unfiltered dumps, filter_wiphy was always initialized to 0, and only interface 0 was dumped. This was introduced in commit 2d75da13fbb957e955d212555b91101cef36f0ce. Reported-by: Arend Van

Re: [PATCH 4/4] ath10k: fix spurious tx/rx during boot

On 08/24/2016 11:18 PM, Michal Kazior wrote: I was looking at firmware to make sure that I fixed what I could there From what I can tell, 10.4 should not have this bug. Did you see this only on 10.1/10.2 firmware? It is of course possible that I am mis-understanding 10.4 I did see

[PATCH] nl80211: initialize state.filter_wiphy in nl80211_dump_interface()

In nl80211_dump_interface() the filter_wiphy variable was set to -1. However, that does not help as message may not contain wiphy or wdev attribute. Instead initialize state.filter_wiphy as is done in nl80211_dump_wiphy(). Fixes: 2d75da13fbb9 ("nl80211: Allow GET_INTERFACE dumps to be filtered")

Re: [PATCH] wlcore: mesh: add zone time sync support

On Sun, 2016-08-21 at 10:13 +, Mishol, Guy wrote: > Kalle/Thomas, > Thanks for your feedback. > > This time sync support is different from the one that mac80211 maintains with > mesh peers. > This time sync is mostly used by upper layers for several applications (like > audio). > In this

[PATCH 0/3] mwifiex: FW downloading debug printing improvements

3 small patches that make FW downloading prints more informative Stanislaw Gruszka (3): mwifiex: make "PCI-E is not the winner" print more informative mwifiex: print status of FW ready event mwifiex: do not print dot when downloading FW drivers/net/wireless/marvell/mwifiex/pcie.c | 9

[PATCH 1/3] mwifiex: make "PCI-E is not the winner" print more informative

Printing ret and adapter->winner do not provide any useful information as those are always 0 at point where the massage is printed. Print value read from reg->fw_status register instead. Stanislaw Gruszka --- drivers/net/wireless/marvell/mwifiex/pcie.c | 3 +-- 1 file

[PATCH 2/3] mwifiex: print status of FW ready event

For debugging purpose print content of reg->fw_status register and other variables values when waiting for firmware ready event. Signed-off-by: Stanislaw Gruszka --- drivers/net/wireless/marvell/mwifiex/pcie.c | 4 1 file changed, 4 insertions(+) diff --git

Re: [PATCH] rt2x00: add support for mac addr from device tree

On Thu, Aug 25, 2016 at 05:03:06PM +0200, Mathias Kresin wrote: > 2016-08-25 15:19 GMT+02:00 Stanislaw Gruszka : > > On Thu, Aug 25, 2016 at 01:12:22PM +0200, Mathias Kresin wrote: > >> 2016-08-25 11:33 GMT+02:00 Stanislaw Gruszka : > >> > On Thu, Aug 25,

Re: rtl8192ce

Larry Finger writes: > On 08/25/2016 08:17 AM, Jes Sorensen wrote: >> Lobachevskii Vitalii writes: >> The realtek devices all require firmwere to operate correctly, >> including the 8192c series. There are a bunch of commands flying back >>

[PATCH 3/3] mwifiex: do not print dot when downloading FW

Printing about 3000 lines like this [ 20.691850] mwifiex_pcie :02:00.0: . [ 20.693466] mwifiex_pcie :02:00.0: . is not useful. If FW downloading will be interrupted, we will get proper error message about that. Signed-off-by: Stanislaw Gruszka ---

Re: [PATCH] rt2x00: add support for mac addr from device tree

2016-08-25 15:19 GMT+02:00 Stanislaw Gruszka : > On Thu, Aug 25, 2016 at 01:12:22PM +0200, Mathias Kresin wrote: >> 2016-08-25 11:33 GMT+02:00 Stanislaw Gruszka : >> > On Thu, Aug 25, 2016 at 10:19:22AM +0200, Mathias Kresin wrote: >> CPE = Customer

Re: rtl8192ce

On 08/25/2016 08:17 AM, Jes Sorensen wrote: Lobachevskii Vitalii writes: Hello, The RTL8192CE device seems to work fine without any firmware, so you may make it fully optional, removing dependency on FW_LOADER. Of course that require some patching, but if I

Re: [PATCH] rt2x00: add support for mac addr from device tree

On Thu, Aug 25, 2016 at 01:12:22PM +0200, Mathias Kresin wrote: > 2016-08-25 11:33 GMT+02:00 Stanislaw Gruszka : > > > > On Thu, Aug 25, 2016 at 10:19:22AM +0200, Mathias Kresin wrote: > > > The EEPROM used on some CPEs has for every device the same generic > > > ralink mac in

Re: rtl8192ce

Lobachevskii Vitalii writes: > Hello, > > The RTL8192CE device seems to work fine without any firmware, so you may > make it fully optional, removing dependency on FW_LOADER. Of course that > require some patching, but if I understood the driver internals > correctly,

Re: brcmfmac43430-sdio.bin in linux-firmware

Hi Arend, On Wed, Aug 24, 2016 at 4:22 PM, Arend Van Spriel wrote: >> Is this something you could help? > > I could, but this is handled by Cypress now. I have asked for firmware > release tag so I can release it. Excellent, thanks for your help!

Re: [PATCH] rt2x00: add support for mac addr from device tree

2016-08-25 11:33 GMT+02:00 Stanislaw Gruszka : > > On Thu, Aug 25, 2016 at 10:19:22AM +0200, Mathias Kresin wrote: > > The EEPROM used on some CPEs has for every device the same generic > > ralink mac in EEPROM and needs to be overridden. > > I don't know what is CPE, but even

rtl8192ce

Hello, The RTL8192CE device seems to work fine without any firmware, so you may make it fully optional, removing dependency on FW_LOADER. Of course that require some patching, but if I understood the driver internals correctly, simple complete(>firmware_loading_complete); would be enough when

Re: pull request: iwlwifi 2016-04-12

On Sun, 2016-08-07 at 07:38 +0300, Emmanuel Grumbach wrote: > On Sun, Aug 7, 2016 at 7:35 AM, Grumbach, Emmanuel > wrote: > > > > > > Hi Kalle, > > > > Here is a pull request for 4.6. I have here a patch that was merged > > to > > -next already, but clearly, it

Re: [PATCH] rt2x00: add support for mac addr from device tree

On Thu, Aug 25, 2016 at 10:19:22AM +0200, Mathias Kresin wrote: > The EEPROM used on some CPEs has for every device the same generic > ralink mac in EEPROM and needs to be overridden. I don't know what is CPE, but even if I would know that, I most likely sill will not understand that description.

[PATCH] rt2x00: add support for mac addr from device tree

The EEPROM used on some CPEs has for every device the same generic ralink mac in EEPROM and needs to be overridden. Signed-off-by: Mathias Kresin --- drivers/net/wireless/ralink/rt2x00/rt2400pci.c | 5 + drivers/net/wireless/ralink/rt2x00/rt2500pci.c | 5 +

Re: iwlwifi errors (regression?) on 4.7.0

Hi Andy, Sorry for the really long delay in replying. :( On Sun, 2016-08-07 at 01:54 -0700, Andy Lutomirski wrote: > My Intel 7265 used to work flawlessly, but for the past week or two > it > has seemed to be very unreliable.  It's also throwing errors.  I see > problems on firmware versions 16

Re: [PATCH 4/4] ath10k: fix spurious tx/rx during boot

On 24 August 2016 at 19:20, Ben Greear wrote: > On 07/19/2016 03:34 AM, Michal Kazior wrote: >> >> HW Rx filters and masks are not configured >> properly by firmware during boot sequences. The >> MAC_PCU_ADDR1 is set to 0s instead of 1s which >> allows the HW to ACK any

Partnership Cooperation

Dear Friend, Your contact details came to me by recommendation, I am interested in investing in your country and I believe you have the capabilities of providing the needed assistance, solutions and advise in actualizing this, Let me know if you are willing to understake this task for me so we