linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Chiu <chiu@endlessm.com>
To: Luca Coelho <luca@coelho.fi>
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: Tue, 7 Nov 2017 12:26:52 +0800	[thread overview]
Message-ID: <CAB4CAwc0G0j1zb+Z4z6iCJ2hzMznUsSVxyF8G3dbZn9pxzffng@mail.gmail.com> (raw)
In-Reply-To: <1509952948.4492.360.camel@coelho.fi>

Hi Luca,
    I just tried the firmware but seems still something wrong. dmesg
shows me the following

[   17.786041] Intel(R) Wireless WiFi driver for Linux
[   17.786042] Copyright(c) 2003- 2015 Intel Corporation
[   18.120052] iwlwifi 0000:00:0c.0: loaded firmware version
33.610294.0 op_mode iwlmvm
[   20.995731] iwlwifi 0000:00:0c.0: Detected Intel(R) Dual Band
Wireless AC 9460, REV=0x318
[   22.012109] iwlwifi 0000:00:0c.0: SecBoot CPU1 Status: 0x3, CPU2
Status: 0x2339
[   22.012115] iwlwifi 0000:00:0c.0: Failed to start INIT ucode: -110
[   22.024100] iwlwifi 0000:00:0c.0: Failed to run INIT ucode: -110

Any more information you need from me?

Chris

On Mon, Nov 6, 2017 at 3:22 PM, Luca Coelho <luca@coelho.fi> wrote:
> On Mon, 2017-11-06 at 11:22 +0800, Chris Chiu wrote:
>> Hi Luca,
>
> Hi Chris,
>
>
>>     Any update for the firmware approval?
>
> Yes, I published it last Thursday.  Sorry, I was in such a hurry that I
>  forgot to tell you about it.
>
> You can find it here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-9260-th-b0-jf-b0-33.ucode?id=f132386b542b52ade0416ecb6cb7aef426f5d175
>
> Let me know how it goes.
>
> --
> Cheers,
> Luca.

  reply	other threads:[~2017-11-07  4:26 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 [this message]
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
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=CAB4CAwc0G0j1zb+Z4z6iCJ2hzMznUsSVxyF8G3dbZn9pxzffng@mail.gmail.com \
    --to=chiu@endlessm.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=linuxwifi@intel.com \
    --cc=luca@coelho.fi \
    /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;
as well as URLs for NNTP newsgroup(s).