From: Luca Coelho <luca@coelho.fi>
To: Chris Chiu <chiu@endlessm.com>
Cc: johannes.berg@intel.com, linuxwifi@intel.com,
linux-wireless@vger.kernel.org,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: Need support for Intel new wifi module 9462NGW
Date: Thu, 16 Nov 2017 11:49:10 +0200 [thread overview]
Message-ID: <1510825750.4011.179.camel@coelho.fi> (raw)
In-Reply-To: <CAB4CAwcwVEyFX=7KJcAT9eXQoof_M+U+tB+FRQCnoP5WgK-MrQ@mail.gmail.com>
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 fixes in
the driver[2]. Please update your system accordingly and let me know
if it works for you.
Thanks!
[1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/
[2] https://patchwork.kernel.org/patch/10059871/
https://patchwork.kernel.org/patch/10059875/
https://patchwork.kernel.org/patch/10059873/
--
Cheers,
Luca.
next prev parent reply other threads:[~2017-11-16 9:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 4:13 Need support for Intel new wifi module 9462NGW Chris Chiu
2017-10-31 7:25 ` Luca Coelho
2017-10-31 7:29 ` Chris Chiu
2017-11-06 3:22 ` Chris Chiu
2017-11-06 7:22 ` Luca Coelho
2017-11-07 4:26 ` Chris Chiu
2017-11-09 3:11 ` Chris Chiu
2017-11-09 6:29 ` Luca Coelho
2017-11-16 9:49 ` Luca Coelho [this message]
2017-11-17 6:39 ` Chris Chiu
2017-11-17 6:46 ` Luca Coelho
2017-11-17 7:23 ` Luca Coelho
2017-11-17 7:38 ` Chris Chiu
2017-11-17 7:53 ` Luca Coelho
2017-11-17 10:14 ` Chris Chiu
2017-11-22 13:48 ` Chris Chiu
2017-11-26 9:49 ` [linuxwifi] " Luca Coelho
2017-11-30 13:18 ` Chris Chiu
2017-12-01 5:29 ` Chris Chiu
2017-12-01 5:53 ` Luca Coelho
2017-12-03 8:39 ` Luca Coelho
2017-12-04 5:36 ` Chris Chiu
2017-12-04 11:43 ` Luca Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1510825750.4011.179.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=chiu@endlessm.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=linuxwifi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.