On Tue, 2017-12-19 at 14:52 +0100, Sedat Dilek wrote: > On Wed, Nov 29, 2017 at 9:20 AM, Luca Coelho <luca@xxxxxxxxx> 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@xxxxxxxxx> > > > 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@xxxxxxxxx > > > > > > > > > > > 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.
