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: Fri, 17 Nov 2017 09:23:14 +0200 [thread overview]
Message-ID: <1510903394.4011.201.camel@coelho.fi> (raw)
In-Reply-To: <1510901207.4011.197.camel@coelho.fi>
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, 2017-11-17 at 14:39 +0800, Chris Chiu wrote:
> > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi>
> > 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
> > > 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
> > > -f
> > > irmware.git/
> > > [2] https://patchwork.kernel.org/patch/10059871/
> > > https://patchwork.kernel.org/patch/10059875/
> > > https://patchwork.kernel.org/patch/10059873/
> > >
> > > --
> > > Cheers,
> > > Luca.
> >
> > Hi Luca,
>
> Hi Chris,
>
>
> > Thanks for your patch and updated firmware. The driver can
> > initialize w/o error now. However, it always fails on ip-config
> > after
> > 4-way handshake complete. I have to mention that I removed the
> > field
> > ".soc_latency" in all new iwl_cfg you added in
> > https://patchwork.kernel.org/patch/10059875/ to remove compile
> > error
> > based on the linux mainline 4.14.
> > I don't know whether if this causes the problem. Do you need me
> > to
> > do anything for more information?
>
> That was my fault, I forgot to include one file in my commit. I have
> sent v2 of the two last patches to solve the problem. Can you try
> them?
>
> The problem you're seeing could be related to that, because we use a
> bit longer wait period for HW stabilization with integrated devices.
> And if you remove it, you may encounter random problems...
>
> --
> Cheers,
> Luca.
next prev parent reply other threads:[~2017-11-17 7:23 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
2017-11-17 6:39 ` Chris Chiu
2017-11-17 6:46 ` Luca Coelho
2017-11-17 7:23 ` Luca Coelho [this message]
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=1510903394.4011.201.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox