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: Thu, 12 Jan 2017 15:19:23 +0530 [thread overview]
Message-ID: <20170112094923.GK3573@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1174 bytes --]
Hi,
Please pull to receive the updated versions of skylake and broxton firmware
binaries.
The following changes since commit 4b9559fb0565f582a21a4070a81a3b6a7d77610b:
linux-firmware: update firmware file for atusb (2016-12-07 01:01:04 +0000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/firmware.git skl
for you to fetch changes up to 4529fb4b320ba8e71a213723d0ad029058b15912:
linux-firmware: intel: Update Broxton audio firmware (2017-01-12 14:58:44 +0530)
----------------------------------------------------------------
Jeeja KP (1):
linux-firmware: intel: Update Skylake audio firmware
Subhransu S. Prusty (1):
linux-firmware: intel: Update Broxton audio firmware
WHENCE | 8 ++++++--
intel/dsp_fw_bxtn.bin | 2 +-
intel/dsp_fw_bxtn_v2010.bin | Bin 0 -> 505608 bytes
intel/dsp_fw_release.bin | 2 +-
intel/dsp_fw_release_v969.bin | Bin 0 -> 221184 bytes
5 files changed, 8 insertions(+), 4 deletions(-)
create mode 100644 intel/dsp_fw_bxtn_v2010.bin
create mode 100644 intel/dsp_fw_release_v969.bin
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2017-01-12 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 9:49 Vinod Koul [this message]
2017-01-13 15:12 ` [GIT PULL] intel: audio firmware updates Kyle McMartin
-- strict thread matches above, loose matches on Subject: below --
2017-08-21 5:20 [GIT PULL]: intel " Vinod Koul
2017-08-23 16:49 ` Kyle McMartin
2016-08-12 11:46 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=20170112094923.GK3573@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).