On Fri, 2017-11-17 at 15:38 +0800, Chris Chiu wrote:
> On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho wrote:
> > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote:
> > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho
> > > wrote:
> > > > Hi Chris,
> > > >
> > > > On Thu, 2017-11-09 at 11:11 +0800,
On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho wrote:
> On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote:
>> On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho wrote:
>> > Hi Chris,
>> >
>> > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote:
>> > > Hi Luca,
>> > > Any suggestion for the "Failed
Here are the links to v2 of the last two patches, please try with these
instead (keep the first one that you already have):
https://patchwork.kernel.org/patch/10060837/
https://patchwork.kernel.org/patch/10060839/
--
Cheers,
Luca.
On Fri, 2017-11-17 at 08:46 +0200, Luca Coelho wrote:
> On Fri,
On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote:
> On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho wrote:
> > Hi Chris,
> >
> > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote:
> > > Hi Luca,
> > > Any suggestion for the "Failed to start INIT ucode: -110"
> > > issue
> > > for the firmwa
On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho wrote:
> Hi Chris,
>
> On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote:
>> Hi Luca,
>> Any suggestion for the "Failed to start INIT ucode: -110" issue
>> for the firmware?
>
> There were a few problems which should now be fixed. We published ne
Hey Folks,
So, for awhile recently, I've noticed my HiKey board (which uses the
TI WL1835MOD chip for wifi) has had trouble when it tries to suspend.
Basically it keeps on waking up while suspending, and then
re-suspending over and over until it lucks out in whatever race is
going on and manages
I have a user interested in getting WDS working on ath10k, but evidently
this is not supported since ath10k uses channel-contexts:
From net/mac80211/main.c:
/*
* WDS is currently prohibited when channel contexts are used
* because there's no clea
Hi all,
ETSI EN-300-328 in version 2.1.1 (2016-11) requires an "adaptive" behaviour of
Wi-Fi Access Points, see clause 4.3.2.6.1 and annex B.7. As far as I
understand this adaptive behavior requires the Wi-Fi card to stop transmitting
whenever an (non Wi-Fi) interference signal with a power lev
On Thu 16 Nov 00:01 PST 2017, Ramon Fried wrote:
> From: Eyal Ilsar
>
> If the value for the firmware configuration parameters
> BTC_STATIC_LEN_LE_BT and BTC_STATIC_LEN_LE_WLAN are not set the duty
> cycle between BT and WLAN is such that if BT (including BLE) is active
> WLAN gets 0 bandwidth.
From: Colin Ian King
In the cases where len is too long, the error return path fails to
kfree allocated buffers buf and usb_reg_buf. The simplest fix is to
perform the sanity check on len before the allocations to avoid having
to do the kfree'ing in the first place.
Detected by CoverityScan, CI
Hi Aditya,
My problem is fixed with this patch. WILC1000 connects to AP,
IP is retrieved from DHCP server and ping works. You can add my
Tested-by: Claudiu Beznea
Thanks,
Claudiu
On 03.11.2017 10:56, Aditya Shankar wrote:
> Commit 46949b48568b ("staging: wilc1000: New cfg packet
> format in ha
Hi Chris,
On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote:
> Hi Luca,
> Any suggestion for the "Failed to start INIT ucode: -110" issue
> for the firmware?
There were a few problems which should now be fixed. We published new
firmwares in our linux-firmware.git tree[1] and also made some
From: Thomas Backlund
iwlwifi 9000 and a series hw contains an extra dash in firmware
file name as seeen in modinfo output for kernel 4.14:
firmware: iwlwifi-9260-th-b0-jf-b0--34.ucode
firmware: iwlwifi-9260-th-a0-jf-a0--34.ucode
firmware: iwlwifi-9000-pu-a0-jf-b0--34.ucode
From: Luca Coelho
A lot of PCI IDs were missing and there were some problems with the
configuration and firmware selection for devices on the 9000 series.
Fix the firmware selection by adding files for the B-steps; add
configuration for some integrated devices; and add a bunch of PCI IDs
(mostly
From: Eyal Ilsar
If the value for the firmware configuration parameters
BTC_STATIC_LEN_LE_BT and BTC_STATIC_LEN_LE_WLAN are not set the duty
cycle between BT and WLAN is such that if BT (including BLE) is active
WLAN gets 0 bandwidth. When tuning these parameters having a too high
value for WLAN
Add non-DFS 5G upper channels (149-165) besides existed 4 lower channels
(36, 40, 44, 48).
{ .band = NL80211_BAND_5GHZ, .center_freq = 5745, .hw_value = 149, },
{ .band = NL80211_BAND_5GHZ, .center_freq = 5765, .hw_value = 153, },
{ .band = NL80211_BAND_5GHZ, .center_freq = 5785, .hw_value = 157, }
16 matches
Mail list logo
