linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: sedat.dilek@gmail.com
Cc: kvalo@codeaurora.org, linux-wireless@vger.kernel.org,
	linuxwifi <linuxwifi@intel.com>
Subject: Re: pull-request: iwlwifi 2017-11-19
Date: Tue, 19 Dec 2017 17:13:54 +0200	[thread overview]
Message-ID: <1513696434.4827.450.camel@coelho.fi> (raw)
In-Reply-To: <CA+icZUUuqoEuvwG9PE8LHT=3vFLf4FmkNUqMUOweE9s-1bcftg@mail.gmail.com>

On Tue, 2017-12-19 at 14:52 +0100, Sedat Dilek wrote:
> On Wed, Nov 29, 2017 at 9:20 AM, Luca Coelho <luca@coelho.fi> wrote:
> > On Wed, 2017-11-29 at 08:51 +0100, Sedat Dilek wrote:
> > > On Tue, Nov 21, 2017 at 11:10 AM, Luca Coelho <luca@coelho.fi>
> > > wrote:
> > > > On Tue, 2017-11-21 at 10:30 +0100, Sedat Dilek wrote:
> > > > > On Mon, Nov 20, 2017 at 12:02 PM, Luca Coelho <luca@coelho.fi
> > > > > >
> > > > > wrote:
> > > > > [..]
> > > > > > ---------------------------------------------------------
> > > > > > ----
> > > > > > ---
> > > > > > iwlwifi: first set of fixes for 4.15
> > > > > > 
> > > > > > * Support new FW API version of scan cmd (used in FW
> > > > > > version
> > > > > > 34);
> > > > > 
> > > > > While seeing this...
> > > > > I have here a iwlwifi-8265 hardware and have seen a recently
> > > > > uploaded
> > > > > FW-version 34 in iwlwifi-firmware Git.
> > > > > Can you explain the dependence of iwlwifi firmware-version /
> > > > > Linux
> > > > > kernel-release and especially probing?
> > > > > Currently, I am using Linux v4.14 from Debian/experimental.
> > > > 
> > > > Mostly for backwards-compatibility, the driver is able to work
> > > > with
> > > > a
> > > > range of firmware versions.  It only uses one of them at a time
> > > > (i.e.
> > > > the highest supported version it finds).
> > > > 
> > > > The driver in v4.14 support version 34 and below.  So it starts
> > > > looking
> > > > for that one and, if not found, falls back to the next lower
> > > > version
> > > > (i.e. 33) and so on, until it finds one.
> > > > 
> > > 
> > > Isn't Linux v4.14.3 (here: -rc1) minimum to completely support
> > > new
> > > features in v34 firmware?
> > 
> > Yes, it is.  But this was a bug and we can't go back and fix
> > v4.14.0-2,
> > right? So it's the best we can do and whoever is using v4.14,
> > should
> > update to v4.14.3 when it comes out to be able to use version 34 of
> > the
> > firmware.
> > 
> 
> Thanks for the confirmation.
> 
> I have added the patch from v4.14.3 to latest Debian-kernel v4.14.2
> and rebuild the corresponding iwlwifi kernel-modules.
> v34 firmware works fine now.
> 
> # dmesg | egrep iwlwifi
> [   21.178769] iwlwifi: loading out-of-tree module taints kernel.
> [   21.184459] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
> [   21.217170] iwlwifi 0000:04:00.0: firmware: direct-loading
> firmware
> iwlwifi-8265-34.ucode
> [   21.218061] iwlwifi 0000:04:00.0: loaded firmware version 34.0.1
> op_mode iwlmvm
> [   21.271000] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band
> Wireless AC 8265, REV=0x230
> [   21.340242] iwlwifi 0000:04:00.0: base HW address:
> bc:a8:a6:d1:3f:49
> [   21.432118] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0

Great! Thanks for confirming.

--
Luca.

      reply	other threads:[~2017-12-19 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 11:02 pull-request: iwlwifi 2017-11-19 Luca Coelho
2017-11-20 15:47 ` Kalle Valo
2017-11-21  9:30 ` Sedat Dilek
2017-11-21 10:10   ` Luca Coelho
2017-11-21 10:42     ` Kalle Valo
2017-11-21 11:37       ` Luca Coelho
2017-11-22 19:46         ` Luis R. Rodriguez
2017-11-22 20:50           ` Luca Coelho
2017-11-23 19:08             ` Luis R. Rodriguez
2017-11-29  7:51     ` Sedat Dilek
2017-11-29  8:20       ` Luca Coelho
2017-12-19 13:52         ` Sedat Dilek
2017-12-19 15:13           ` Luca Coelho [this message]

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=1513696434.4827.450.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=sedat.dilek@gmail.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;
as well as URLs for NNTP newsgroup(s).