From: Peter Xu <peterx@redhat.com>
To: Luca Coelho <luca@coelho.fi>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: Intel Wireless 7260 failed to work
Date: Wed, 28 Dec 2016 16:10:39 +0800 [thread overview]
Message-ID: <20161228081039.GA3874@pxdev.xzpeter.org> (raw)
In-Reply-To: <1482910035.8602.3.camel@coelho.fi>
On Wed, Dec 28, 2016 at 09:27:15AM +0200, Luca Coelho wrote:
[...]
> > > > Is this a known issue? Please let me know if anyone wants more info or
> > > > logs, since this error triggers easily (everytime I boot).
> > >
> > > The error message isn't really telling much to the user (hint hint) but
> > > I suspect this is by design:
> > >
> > > "iwlwifi: remove support for fw older than -17 and -22
>
> Right, we only maintain support for a certain number of firmware
> versions. The FW APIs change with time and we don't want to keep all
> legacy code supporting old firmwares in the driver forever.
>
> I agree that "no suitable firmware found!" is a bit scarce. I'll see
> if we can improve that with something: "no suitable firmware found! You
> need iwlwifi-7260-17.ucode (<link to git>)".
That'll be great if we can have this info in the log. Maybe no need
for a full URL, the firmware name would suffice at least for me.
[...]
> I don't think we are very aggressive, we have been supporting -17 since
> v4.3:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5865f3658ba37c54e346b0fdee08a1c7a152681b
>
> And we have published the firmware about half a year ago:
>
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-7260-17.ucode?id=f2cf4d67e8eced29c8a473d3a27057aa2df57c42
>
> I understand your concern, but if you want to be on the bleeding-edge
> kernel, you should be on the bleeding-edge linux-firmware as well. ;)
Fair enough. :-)
>
> But as I said, I'll try to improve the error message, as that should
> make it easier to figure out.
Thank you!
-- peterx
next prev parent reply other threads:[~2016-12-28 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 9:17 Intel Wireless 7260 failed to work Peter Xu
2016-12-27 16:41 ` Larry Finger
2016-12-28 3:50 ` Peter Xu
2016-12-27 19:46 ` Kalle Valo
2016-12-28 3:59 ` Peter Xu
2016-12-28 7:27 ` Luca Coelho
2016-12-28 8:10 ` Peter Xu [this message]
2016-12-28 8:17 ` Emmanuel Grumbach
2016-12-28 8:37 ` Luca Coelho
2016-12-28 12:13 ` Kalle Valo
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=20161228081039.GA3874@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 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.