Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup

Daniel Lenski writes: > On Fri, May 20, 2016 at 1:50 PM, Daniel Lenski wrote: >> Am I understanding your idea correctly? To put a loop around the 8051 >> reset and the firmware polling loop, with a delay between failure and retry? > > That was some sloppy

Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup

On Fri, May 20, 2016 at 7:08 AM, Jes Sorensen wrote: > > Daniel Lenski writes: > > Unfortunately, I ran into a case today where even 5000 loops was not > > enough after a cold boot. 5000 loops meant about 1.5 second delay > > between finishing the

Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

From: Kalle Valo Date: Thu, 19 May 2016 15:45:08 +0300 > this the second version of the last pull request to net-next for 4.7, > which got postponed due to the recent iwlwifi merge conflict. Now that > Linus fixed the merge problem in his tree I actually didn't have to fix

Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup

On Fri, May 20, 2016 at 1:50 PM, Daniel Lenski wrote: > Am I understanding your idea correctly? To put a loop around the 8051 > reset and the firmware polling loop, with a delay between failure and retry? That was some sloppy pseudo-code by me... here's what I think you're

Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup

Jes Sorensen writes: > > Unfortunately, I ran into a case today where even 5000 loops was not > > enough after a cold boot. 5000 loops meant about 1.5 second delay > > between finishing the firmware checksum poll, while waiting for the > > firmware to start. It now

Re: updating carl9170-1.fw in linux-firmware.git

On 04/20/2016 11:11 PM, Christian Lamparter wrote: > On Wednesday, April 20, 2016 10:59:44 AM Kalle Valo wrote: >> Christian Lamparter writes: >> >>> On Monday, April 18, 2016 07:42:05 PM Kalle Valo wrote: Christian Lamparter writes:

Re: "kernel: BUG: scheduling while atomic:" errors with linux kernel 4.6

On 05/19/2016 05:56 PM, Bob Copeland wrote: +linux-wireless On Thu, May 19, 2016 at 03:11:16PM -0600, James Feeney wrote: Arch linux 4.6-1 wpa_supplicant 1:2.5-3 Toshiba Satellite, circa 2011, with a Pentium Dual-Core Mobile Error is not seen on other machines. kernel: BUG: scheduling while

[PATCH 2/2] ath10k: Add board data download from target

The QCA9887 stores its calibration data (board.bin) inside the EEPROM of the target. This has to be downloaded manually to allow the device to initialize correctly. Signed-off-by: Sven Eckelmann --- drivers/net/wireless/ath/ath10k/core.c | 41 +-

[PATCH 0/2] ath10k: Add support for QCA9887

Hi, the QCA9887 chip is similar to the QCA988x chips. But it requires a special firmware and uses a different calibration data source. Unfortunately, no working firmware currently exists. But it is possible to create a semi working one by binary patching the current version. # download new

[PATCH 1/2] ath10k: add QCA9887 chipset support

Add the hardware name, revision, firmware names and update the pci_id table. QA9887 HW1.0 is supposed to be similar to QCA988X HW2.0 . Details about he firmware interface are currently unknown. Signed-off-by: Sven Eckelmann ---

Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup

Daniel Lenski writes: > You're welcome, and thanks for writing this great driver. It really > makes a huge difference for stability of the Yoga 13 wifi! You're welcome! It made a big difference for my own Yoga 13 and it's been an exciting project. I learned a lot in the

[PATCH 1/2] ath10k: Remove duplicate and unused rx rate flags

From: Mohammed Shafi Shajakhan All these flags are not used and their use is completely covered by 'ath10k_hw_rate_ofdm', 'ath10k_hw_rate_cck', and RX_PPDU_START_RATE_FLAG Signed-off-by: Mohammed Shafi Shajakhan --- [thanks

[PATCH 2/2] ath10k: Fix CCK h/w rates for QCA99X0 and newer chipsets

From: Mohammed Shafi Shajakhan CCK hardware table mapping from QCA99X0 onwards got revised. The CCK hardware rate values are in a proper order wrt. to rate and preamble as below ATH10K_HW_RATE_REV2_CCK_LP_1M = 1, ATH10K_HW_RATE_REV2_CCK_LP_2M = 2,

Re: Who is the maintainer of net/wireless/wext* ?

On Fri, 2016-05-20 at 12:34 +0200, Sedat Dilek wrote: > On 5/20/16, Ujjal Roy wrote: > > > > I want to know the maintainer of > > > > net/wireless/wext*. Please any reply. > > > For example, you can look in the MAINTAINERS file. > > CFG80211 and NL80211 > M:Johannes

[PATCH V2 4.8 2/2] brcmfmac: support get_channel cfg80211 callback

This is important for brcmfmac as some of released firmwares (e.g. brcmfmac4366b-pcie.bin) may pick different channel than requested. This has been tested with BCM4366B1 in D-Link DIR-885L. Signed-off-by: Rafał Miłecki --- V2: Check if ndev isn't NULL, update description. ---

[PATCH V2 4.8 1/2] brcmutil: add field storing control channel to the struct brcmu_chan

Our d11 code supports encoding/decoding channel info into/from chanspec format used by firmware. Current implementation is quite misleading because of the way "chnum" field is used. When encoding channel info, "chnum" has to be filled by a caller with *center* channel number. However when decoding

Re: [PATCH 4.8 2/2] brcmfmac: support get_channel cfg80211 callback

On 20 May 2016 at 09:42, Arend Van Spriel wrote: > On 19-5-2016 13:02, Rafał Miłecki wrote: >> This is important for brcmfmac as the firmware may pick different >> channel than requested. This has been tested with BCM4366B1 (in D-Link >> DIR-885L). > > Can you

Re: Who is the maintainer of net/wireless/wext* ?

On 05/20/2016 12:34 PM, Sedat Dilek wrote: > On 5/20/16, Ujjal Roy wrote: >> I want to know the maintainer of >> >> net/wireless/wext*. Please any reply. >> > > For example, you can look in the MAINTAINERS file. > > CFG80211 and NL80211 > M:Johannes Berg

Re: Who is the maintainer of net/wireless/wext* ?

On 5/20/16, Ujjal Roy wrote: > I want to know the maintainer of > > net/wireless/wext*. Please any reply. > For example, you can look in the MAINTAINERS file. CFG80211 and NL80211 M: Johannes Berg L: linux-wireless@vger.kernel.org W:

Who is the maintainer of net/wireless/wext* ?

I want to know the maintainer of net/wireless/wext*. Please any reply. Thanks, UjjaL Roy -- 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

[PATCH iw] add "channels" PHY command listing frequencies with more details

Channels (frequencies) are getting more details that users may want to know about. E.g. it's important to know which frequencies allow using 40/80/160 MHz channels to setup AP properly. We list channels in "info" command output but it's already quite big and it was agreed to introduce new command

Re: [PATCH] brcmfmac: use kmemdup

On 19-5-2016 15:59, Muhammad Falak R Wani wrote: > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. Acked-by: Arend van Spriel > Signed-off-by:

Re: [PATCH 4.8 1/2] brcmutil: add field storing control channel to the struct brcmu_chan

On 19-5-2016 13:02, Rafał Miłecki wrote: > Our d11 code supports encoding/decoding channel info into/from chanspec > format used by firmware. Current implementation is quite misleading > because of the way "chnum" field is used. > When encoding channel info, "chnum" has to be filled by a caller

Re: [PATCH 4.8 2/2] brcmfmac: support get_channel cfg80211 callback

On 19-5-2016 13:02, Rafał Miłecki wrote: > This is important for brcmfmac as the firmware may pick different > channel than requested. This has been tested with BCM4366B1 (in D-Link > DIR-885L). Can you elaborate? Is this for AP or STA mode? > Signed-off-by: Rafał Miłecki >