alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: linux-firmware@kernel.org
Cc: Patches Audio <patches.audio@intel.com>, alsa-devel@alsa-project.org
Subject: [GIT PULL]: intel audio firmware updates
Date: Mon, 21 Aug 2017 10:50:48 +0530	[thread overview]
Message-ID: <20170821052042.GH3053@localhost> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2337 bytes --]

Hi,

Please pull to receive updated KBL audio firmware. Along with this time for
some cleaning of the exiting files and remove no longer used SKL and BXT
fw files.

The following changes since commit 7d2c913dcd1be083350d97a8cb1eba24cfacbc8a:

  ath10k: update year in license (2017-06-22 12:06:02 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/firmware.git intel

for you to fetch changes up to 7b7513e03eb6949f39fba2eb4b661c31f8ea6f5b:

  linux-firmware: intel: remove old broxton firmware (2017-08-21 10:35:32 +0530)

----------------------------------------------------------------
Subhransu S. Prusty (1):
      linux-firmware: intel: Update Kabylake audio firmware

Vinod Koul (2):
      linux-firmware: intel: remove old skylake firmware
      linux-firmware: intel: remove old broxton firmware

 WHENCE                        |  26 +++-----------------------
 intel/dsp_fw_bxtn_v1118.bin   | Bin 505608 -> 0 bytes
 intel/dsp_fw_bxtn_v2010.bin   | Bin 505608 -> 0 bytes
 intel/dsp_fw_bxtn_v430.bin    | Bin 505608 -> 0 bytes
 intel/dsp_fw_bxtn_v702.bin    | Bin 505608 -> 0 bytes
 intel/dsp_fw_kbl.bin          |   2 +-
 intel/dsp_fw_kbl_v2630.bin    | Bin 0 -> 243016 bytes
 intel/dsp_fw_release_v827.bin | Bin 233472 -> 0 bytes
 intel/dsp_fw_release_v869.bin | Bin 233472 -> 0 bytes
 intel/dsp_fw_release_v896.bin | Bin 233472 -> 0 bytes
 intel/dsp_fw_release_v927.bin | Bin 233472 -> 0 bytes
 intel/dsp_fw_release_v948.bin | Bin 221184 -> 0 bytes
 intel/dsp_fw_release_v951.bin | Bin 221184 -> 0 bytes
 intel/dsp_fw_release_v958.bin | Bin 221184 -> 0 bytes
 14 files changed, 4 insertions(+), 24 deletions(-)
 delete mode 100644 intel/dsp_fw_bxtn_v1118.bin
 delete mode 100644 intel/dsp_fw_bxtn_v2010.bin
 delete mode 100644 intel/dsp_fw_bxtn_v430.bin
 delete mode 100644 intel/dsp_fw_bxtn_v702.bin
 create mode 100644 intel/dsp_fw_kbl_v2630.bin
 delete mode 100644 intel/dsp_fw_release_v827.bin
 delete mode 100644 intel/dsp_fw_release_v869.bin
 delete mode 100644 intel/dsp_fw_release_v896.bin
 delete mode 100644 intel/dsp_fw_release_v927.bin
 delete mode 100644 intel/dsp_fw_release_v948.bin
 delete mode 100644 intel/dsp_fw_release_v951.bin
 delete mode 100644 intel/dsp_fw_release_v958.bin

Thanks
-- 
~Vinod

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2017-08-21  5:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  5:20 Vinod Koul [this message]
2017-08-23 16:49 ` [GIT PULL]: intel audio firmware updates Kyle McMartin
  -- strict thread matches above, loose matches on Subject: below --
2017-01-12  9:49 [GIT PULL] intel: " Vinod Koul
2017-01-13 15:12 ` Kyle McMartin
2016-08-12 11:46 [GIT PULL]: intel " Vinod Koul
2016-08-15 14:48 ` Kyle McMartin

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=20170821052042.GH3053@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-firmware@kernel.org \
    --cc=patches.audio@intel.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).