From: Luca Coelho <luca@coelho.fi>
To: "Artem S. Tashkinov" <t.artem@lycos.com>, linux-wireless@vger.kernel.org
Subject: Re: Please release/publish iwlwifi-7265D-26.ucode iwlwifi-7265D-25.ucode iwlwifi-7265D-24.ucode iwlwifi-7265D-23.ucode
Date: Wed, 29 Mar 2017 14:00:25 +0300 [thread overview]
Message-ID: <1490785225.13345.8.camel@coelho.fi> (raw)
In-Reply-To: <910ef9cb656db856dd78a919803860b8@lycos.com>
On Mon, 2017-03-27 at 16:53 +0500, Artem S. Tashkinov wrote:
> Hi,
>
> New versions of iwlwifi require the firmware files which have never been
> released by Intel.
>
> Please fix this bummer.
>
> iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-26.ucode
> failed with error -2
> iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-25.ucode
> failed with error -2
> iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode
> failed with error -2
> iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode
> failed with error -2
> iwlwifi 0000:02:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
We always keep our mainline driver very close to our development trees.
In the development trees we are updating the versions periodically and
we don't know which ones we are going to release publicly.
If we don't try to load newer versions when a kernel version is
released, and later decide to publish the newer firmware versions, it
won't work. This is the explanation. :)
And actually, we try to load these newer firmwares, but if they are not
present, we fall back to the older one. You can see that we correctly
loaded version 22 (the last line in your traces).
Now, these error messages to look annoying. But fortunately Luis
Rodriguez is already attempting to fix that in another patch series.
HTH.
--
Cheers,
Luca.
prev parent reply other threads:[~2017-03-29 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:53 Please release/publish iwlwifi-7265D-26.ucode iwlwifi-7265D-25.ucode iwlwifi-7265D-24.ucode iwlwifi-7265D-23.ucode Artem S. Tashkinov
2017-03-29 11:00 ` 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=1490785225.13345.8.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=t.artem@lycos.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.