From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Dusan Bruncko <dusan.bruncko@cern.ch>
Cc: linux-wireless@vger.kernel.org, centos-devel@centos.org
Subject: Re: iwlwifi-7265-ucode-25.30.14.0.tgz. in Centos 7
Date: Tue, 10 Apr 2018 13:00:13 +0200 [thread overview]
Message-ID: <20180410110012.GB4284@redhat.com> (raw)
In-Reply-To: <fe3605be-8ce1-ee6f-7ea2-7f736f5493fb@cern.ch>
On Sun, Apr 08, 2018 at 08:58:35AM +0200, Dusan Bruncko wrote:
> My problem is following: This firmware was created for kernel 4.2+,
> but I am using
> Centos 7 with kernels a la 3.10. Therefore I see during booting and
Wireless stack and drivers are regularly updated in Centos kernel,
(for example latest release has wireless drivers from 4.14)
and should match firmware provided in the distribution.
Regards
Stanislaw
prev parent reply other threads:[~2018-04-10 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 6:58 iwlwifi-7265-ucode-25.30.14.0.tgz. in Centos 7 Dusan Bruncko
2018-04-09 0:31 ` Larry Finger
2018-04-09 4:56 ` Dusan Bruncko
2018-04-09 16:18 ` Larry Finger
2018-04-09 18:21 ` Arend van Spriel
2018-04-10 11:00 ` Stanislaw Gruszka [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=20180410110012.GB4284@redhat.com \
--to=sgruszka@redhat.com \
--cc=centos-devel@centos.org \
--cc=dusan.bruncko@cern.ch \
--cc=linux-wireless@vger.kernel.org \
/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).