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: [linuxwifi] Need support for Intel new wifi module 9462NGW
Date: Mon, 4 Dec 2017 13:36:52 +0800	[thread overview]
Message-ID: <CAB4CAwd68miZHrVxhx2nGey-6685+19d4wXvhCux1KER+j1KNQ@mail.gmail.com> (raw)
In-Reply-To: <1512290364.4827.57.camel@coelho.fi>

Hi Luca,
    I applied https://patchwork.kernel.org/patch/10088929/ and
https://patchwork.kernel.org/patch/10088939/, I can access internet
thru 9461/9462NGW now. Thanks so much.

Chris

On Sun, Dec 3, 2017 at 4:39 PM, Luca Coelho <luca@coelho.fi> wrote:
> On Fri, 2017-12-01 at 07:53 +0200, Luca Coelho wrote:
>> On Fri, 2017-12-01 at 13:29 +0800, Chris Chiu wrote:
>> > Hi Luca,
>> >     I think the problem is not missing DHCP reply. I installed
>> > tcpdump
>> > on the machine with Intel 9461NGW and start monitoring on the wlan
>> > interface.
>> > The result is following
>> > https://gist.github.com/mschiu77/f4cc14ddae6adf137da15675cca59b30
>> >
>> > I also attach the ifconfig result at the end of the above url. Hope
>> > this can help a little.
>>
>> Hi Chris,
>>
>> Sorry for the delay.  We've been testing this internally, but
>> couldn't
>> reproduce it at first.  The problems seems to be with the firmware
>> that
>> we released.
>>
>> I'll provide you an update today or latest by Monday next week.
>
> Hi Chris,
>
> We found a patch that was missing from upstream and causes data
> corruption on secure associations:
>
> https://patchwork.kernel.org/patch/10088939/
>
>
> Can you try to apply this patch and see if it fixes the problem you are
> having?
>
> --
> Cheers,
> Luca.

  reply	other threads:[~2017-12-04  5:36 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
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 [this message]
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=CAB4CAwd68miZHrVxhx2nGey-6685+19d4wXvhCux1KER+j1KNQ@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).