Re: [PATCH] mac80211: Update last_ack status for all except probing frames

On 10/30/2017 05:29 PM, Rajkumar Manoharan wrote: Update last_ack status for all except station probing frames (i.e null data). Otherwise the station inactivity duration is cleared whenever AP is checking presence of idle stations by sending null data frame for every inactive threshold

Re: pull-request: wireless-drivers 2017-10-31

From: Kalle Valo Date: Tue, 31 Oct 2017 17:19:24 +0200 > here's a pull request to net tree for 4.14. Due to the ath10k security > issue I would like to get this to 4.14 still. > > Please let me know if there are any problems. Pulled, thanks a lot.

Re: rtlwifi oops

On 10/31/2017 06:11 AM, Barry Day wrote: On Sun, Oct 29, 2017 at 01:08:24AM +0300, nirinA raseliarison wrote: [ 145.966016] usb 2-1.4: new high-speed USB device number 4 using ehci-pci [ 146.045808] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8178 [ 146.045811] usb 2-1.4: New

Re: iwlwifi crash with hostapd

On 31.10.2017 20:25, Mario Theodoridis wrote: Hi James, On 24.10.2017 23:01, James Cameron wrote: But it is only a warning.  If connections aren't dying, it may not be important to you. Regarding whether wifi hangs, it's usually takes a while to get going and then disappears. Sunday

Re: iwlwifi crash with hostapd

Hi James, On 24.10.2017 23:01, James Cameron wrote: But it is only a warning. If connections aren't dying, it may not be important to you. Regarding whether wifi hangs, it's usually takes a while to get going and then disappears. Sunday night i ended up rebooting into the 4.4-79 kernel

Re: [PATCH v2] wireless-regdb: Add 5 Ghz rules for Kazakhstan (KZ)

On Tue, Oct 31, 2017 at 11:39:13PM +0600, WoWz89 wrote: > Здравствуйте, Seth. > > Вы писали 20 октября 2017 г., 21:06:51: > > > Add rules for 5150-5250 MHz, 5250-5350 MHz, and 5470-5725 Mhz > > based on the documents at [1] and [2]. > > > v2: Also add DFS region > Good afternoon, when will the

Re: [v3,1/3] rsi: sdio: add WOWLAN support for S3 suspend state

On Tue, Oct 31, 2017 at 8:54 PM, Kalle Valo wrote: > Kalle Valo writes: > >> Amitkumar Karwar wrote: >> >>> From: Karun Eagalapati >>> >>> WoWLAN is supported in RS9113 device through GPIO pin2. >>> wowlan

Re: [PATCH v2] wireless-regdb: Add 5 Ghz rules for Kazakhstan (KZ)

Здравствуйте, Seth. Вы писали 20 октября 2017 г., 21:06:51: > Add rules for 5150-5250 MHz, 5250-5350 MHz, and 5470-5725 Mhz > based on the documents at [1] and [2]. > v2: Also add DFS region Good afternoon, when will the update ? > [1] >

Re: PROBLEM: Issue with wireless driver after resume from suspend.

On Tue, Oct 31, 2017 at 7:51 AM, Anil Nair wrote: > Hi All, > > I am having a issue with the wireless driver in my laptop. Attached > information > pertaining to the issue. > > [1.] One line summary of the problem: > > Wifi not working after resuming from suspend state.

Re: ath10k: Wifi slow on the XPS13 (9360) (QCA6174)

Lo! On 29.10.2017 08:27, Kalle Valo wrote: > [..] > sorry for the late reply, I'm having problems keeping up with all the > email. No worries, this problem is nothing new, I just thought it might be good to finally bring this to ath10k, as I got the impressions it had not gotten proper attention

RE: [EXT] Re: pull-request mwifiex-firmware 2017-10-30

Hi Brian, > -Original Message- > From: Brian Norris [mailto:briannor...@chromium.org] > Sent: Tuesday, October 31, 2017 1:18 AM > To: Ganapathi Bhat > Cc: linux-firmw...@kernel.org; linux-wireless@vger.kernel.org; James Cao; > Cathy Luo; Mangesh Malusare; Xinming Hu; Zhiyuan Yang; Karthik

pull-request mwifiex-firmware 2017-10-31

The following changes since commit e0494e95192ac5329989f4d128cf95c417d618cc: linux-firmware: update Marvell PCIe-USB8997 firmware image (2017-08-01 23:55:30 +0530) are available in the git repository at: git://git.marvell.com/mwifiex-firmware.git for you to fetch changes up to

pull-request mwifiex-firmware 2017-10-31

The following changes since commit e0494e95192ac5329989f4d128cf95c417d618cc: linux-firmware: update Marvell PCIe-USB8997 firmware image (2017-08-01 23:55:30 +0530) are available in the git repository at: git://git.marvell.com/mwifiex-firmware.git for you to fetch changes up to

Re: [v3,1/3] rsi: sdio: add WOWLAN support for S3 suspend state

Kalle Valo writes: > Amitkumar Karwar wrote: > >> From: Karun Eagalapati >> >> WoWLAN is supported in RS9113 device through GPIO pin2. >> wowlan config frame is internally sent to firmware in mac80211 >> suspend handler. Also

pull-request: wireless-drivers 2017-10-31

Hi Dave, here's a pull request to net tree for 4.14. Due to the ath10k security issue I would like to get this to 4.14 still. Please let me know if there are any problems. Kalle The following changes since commit a6127b4440d1f74f26b64006b2f50c9dc6d66efc: Merge tag

Re: [v3] ath10k: rebuild crypto header in rx data frames

Am 31.10.2017 um 16:00 schrieb Kalle Valo: Sebastian Gottschall writes: the following patchlines in the v3 patch look wrong +   /* ICV */ +   if (status->flag & RX_FLAG_ICV_STRIPPED && +   enctype !=

Re: [v3] ath10k: rebuild crypto header in rx data frames

Sebastian Gottschall writes: > the following patchlines in the v3 patch look wrong > > +   /* ICV */ > +   if (status->flag & RX_FLAG_ICV_STRIPPED && > +   enctype != HTT_RX_MPDU_ENCRYPT_AES_CCM_WPA2) > +  

Re: [v3] ath10k: rebuild crypto header in rx data frames

Sorry top posting. The issues in raw mode with CCMP-256, GCMP and GCMP-256 were already known and the same was captured in the commit log. As mentioned in the commit log, raw mode with these ciphers does not work even without this particular patch and it needs some cleanup like done in the

Re: [v3] ath10k: rebuild crypto header in rx data frames

the same is for the MIC +   /* MIC */ +   if ((status->flag & RX_FLAG_MIC_STRIPPED) && +   enctype == HTT_RX_MPDU_ENCRYPT_AES_CCM_WPA2) +   skb_trim(msdu, msdu->len - 8); this code looks wrong too Am 30.10.2017 um 10:32 schrieb

Re: [v3] ath10k: rebuild crypto header in rx data frames

the following patchlines in the v3 patch look wrong +   /* ICV */ +   if (status->flag & RX_FLAG_ICV_STRIPPED && +   enctype != HTT_RX_MPDU_ENCRYPT_AES_CCM_WPA2) +   skb_trim(msdu, msdu->len - +   

[PATCH v3 1/3] mac80211: Add TXQ scheduling API

This adds an API to mac80211 to handle scheduling of TXQs and changes the interface between driver and mac80211 for TXQ handling as follows: - The wake_tx_queue callback interface no longer includes the TXQ. Instead, the driver is expected to retrieve that from ieee80211_next_txq() - Two new

[PATCH v3 3/3] ath9k: Switch to mac80211 airtime API

This removes the in-driver airtime fairness scheduling from ath9k and switches the driver to use the API introduced in mac80211 in the previous commit. Signed-off-by: Toke Høiland-Jørgensen --- drivers/net/wireless/ath/ath9k/ath9k.h | 7 +---

[PATCH v3 2/3] mac80211: Add airtime account and scheduling to TXQs

This adds airtime accounting and scheduling to the mac80211 TXQ scheduler. A new hardware flag, AIRTIME_ACCOUNTING, is added that drivers can set if they support reporting airtime usage of transmissions. When this flag is set, mac80211 will expect the actual airtime usage to be reported in the

[PATCH 3/3] mwifiex: cleanup rx_reorder_tbl_lock usage

From: Karthik Ananthapadmanabha Fix the incorrect usage of rx_reorder_tbl_lock spinlock: 1. We shouldn't access the fields of the elements returned by mwifiex_11n_get_rx_reorder_tbl() after we have released spin lock. To fix this, To fix this, aquire the spinlock before

[PATCH 2/3] mwifiex: cleanup tx_ba_stream_tbl_lock usage

From: Karthik Ananthapadmanabha Fix the incorrect usage of tx_ba_stream_tbl_lock spinlock: 1. We shouldn't access the fields of the elements returned by mwifiex_get_ba_status() and mwifiex_get_ba_tbl(), after we have released the spin lock. To fix this, aquire the spinlock

[PATCH 0/3] mwifiex: fix usage issues with spinlocks

This patch series fixes issues with usage of few of the spinlocks used by the driver. To summarise it fixes below issues: 1. Driver does access the elements returned by the list, without acquiring the lock. 2. Driver release the lock during iteration of the list and hold it back before starting

[PATCH 1/3] mwifiex: cleanup rx_pkt_lock usage in 11n_rxreorder.c

From: Karthik Ananthapadmanabha Fix the incorrect usage of rx_pkt_lock spinlock. Realsing the spinlock while the element is still in process is unsafe. The lock must be released only after the element processing is complete. Signed-off-by: Karthik Ananthapadmanabha

Re: PROBLEM: Issue with wireless driver after resume from suspend.

Luca Coelho writes: >> I am having a issue with the wireless driver in my laptop. Attached >> information >> pertaining to the issue. > > It would be useful to specify which wireless card you are using. In > this case, the problem seems to be with ath10k. For ath10k issues

Re: Need support for Intel new wifi module 9462NGW

Great. Thanks. On Tue, Oct 31, 2017 at 3:25 PM, Luca Coelho wrote: > On Tue, 2017-10-31 at 12:13 +0800, Chris Chiu wrote: >> Hi, > > Hi Chris, > > >> We just have the Intel new WiFi module 9462NGW from Acer and >> tried >> to verify if it works on the latest linux kernel.

Re: Need support for Intel new wifi module 9462NGW

On Tue, 2017-10-31 at 12:13 +0800, Chris Chiu wrote: > Hi, Hi Chris, > We just have the Intel new WiFi module 9462NGW from Acer and > tried > to verify if it works on the latest linux kernel. Unfortunately it > seems not even detected because the PCI ID seems unknown to the > iwlwifi

Re: PROBLEM: Issue with wireless driver after resume from suspend.

On Tue, 2017-10-31 at 12:21 +0530, Anil Nair wrote: > Hi All, Hi, > I am having a issue with the wireless driver in my laptop. Attached > information > pertaining to the issue. It would be useful to specify which wireless card you are using. In this case, the problem seems to be with ath10k.

PROBLEM: Issue with wireless driver after resume from suspend.

Hi All, I am having a issue with the wireless driver in my laptop. Attached information pertaining to the issue. [1.] One line summary of the problem: Wifi not working after resuming from suspend state. [2.] Full description of the problem/report: I had put my laptop in suspend