linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: "linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kyle@infradead.org" <kyle@infradead.org>,
	"jwboyer@kernel.org" <jwboyer@kernel.org>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>,
	golan.ben.ami@intel.com,
	You-Sheng Yang <vicamo.yang@canonical.com>
Subject: pull request: iwlwifi firmware updates 2021-11-01
Date: Mon, 01 Nov 2021 15:58:01 +0200	[thread overview]
Message-ID: <19391a6dd10076e3a64aff20d68a9a37ac56e794.camel@coelho.fi> (raw)

[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]

Hi,

This contains some new and updated firmwares for all our currently
maintained FW binaries.

Please pull or let me know if there are any issues.

--
Cheers,
Luca.


The following changes since commit b21eb2607f167408b780d1360431a93525e9f229:

  amdgpu: update VCN firmware for green sardine (2021-10-28 10:07:10 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git tags/iwlwifi-fw-2021-11-01

for you to fetch changes up to 4474519a1fd4e7167afae7c5ca2c1b93e17b4d8a:

  iwlwifi: add new FWs from core64-96 release (2021-11-01 15:50:49 +0200)

----------------------------------------------------------------
Update and add iwlwifi firmware binaries for release Core64-96.

----------------------------------------------------------------
Luca Coelho (2):
      iwlwifi: update 9000-family firmwares to core64-96
      iwlwifi: add new FWs from core64-96 release

 WHENCE                            |  21 +++++++++++++++++++--
 iwlwifi-9000-pu-b0-jf-b0-46.ucode | Bin 1514876 -> 1519264 bytes
 iwlwifi-9260-th-b0-jf-b0-46.ucode | Bin 1485620 -> 1490096 bytes
 iwlwifi-QuZ-a0-hr-b0-67.ucode     | Bin 0 -> 1347524 bytes
 iwlwifi-cc-a0-67.ucode            | Bin 0 -> 1310488 bytes
 iwlwifi-so-a0-gf-a0-67.ucode      | Bin 0 -> 1524432 bytes
 iwlwifi-so-a0-gf-a0.pnvm          | Bin 41804 -> 41804 bytes
 iwlwifi-so-a0-gf4-a0-67.ucode     | Bin 0 -> 1541932 bytes
 iwlwifi-so-a0-gf4-a0.pnvm         | Bin 0 -> 21576 bytes
 iwlwifi-ty-a0-gf-a0-67.ucode      | Bin 0 -> 1482872 bytes
 iwlwifi-ty-a0-gf-a0.pnvm          | Bin 27480 -> 41612 bytes
 11 files changed, 19 insertions(+), 2 deletions(-)
 create mode 100644 iwlwifi-QuZ-a0-hr-b0-67.ucode
 create mode 100644 iwlwifi-cc-a0-67.ucode
 create mode 100644 iwlwifi-so-a0-gf-a0-67.ucode
 create mode 100644 iwlwifi-so-a0-gf4-a0-67.ucode
 create mode 100644 iwlwifi-so-a0-gf4-a0.pnvm
 create mode 100644 iwlwifi-ty-a0-gf-a0-67.ucode


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2021-11-01 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 13:58 Luca Coelho [this message]
2021-11-01 13:58 ` pull request: iwlwifi firmware updates 2021-11-01 Luca Coelho
2021-11-01 14:43 ` Josh Boyer
2022-01-17 15:26 ` youling257

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=19391a6dd10076e3a64aff20d68a9a37ac56e794.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=ben@decadent.org.uk \
    --cc=golan.ben.ami@intel.com \
    --cc=jwboyer@kernel.org \
    --cc=kyle@infradead.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vicamo.yang@canonical.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 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).