From: Luca Coelho <firstname.lastname@example.org>
To: Emmanuel Grumbach <email@example.com>, Peter Xu <firstname.lastname@example.org>
Cc: Kalle Valo <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Subject: Re: Intel Wireless 7260 failed to work
Date: Wed, 28 Dec 2016 10:37:05 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On Wed, 2016-12-28 at 10:17 +0200, Emmanuel Grumbach wrote:
> On Wed, Dec 28, 2016 at 10:10 AM, Peter Xu <firstname.lastname@example.org> wrote:
> > 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.
> In this case, I think we should also print the range that is supported
> when we fail to find any suitable firmware.
Sure, I'll do that. I just wanted to keep it simple in this thread. ;)
next prev parent reply other threads:[~2016-12-28 8:37 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
2016-12-28 8:17 ` Emmanuel Grumbach
2016-12-28 8:37 ` Luca Coelho [this message]
2016-12-28 12:13 ` Kalle Valo
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).