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]: Update sst audio firmware for Skylake
Date: Thu, 4 Feb 2016 10:42:27 +0530 [thread overview]
Message-ID: <20160204051227.GP11744@localhost> (raw)
Hello Linux firmware maintainers,
Please PULL to receive the updated version of Skylake audio firmware.
This PULL request has two patches, first one creates a sym link for binary
name which helps us to keep different versions of firmware in git
Second one updates to latest FW v869
The following changes since commit 52442afee9907bc32a058f22bb3295d040677c26:
brcm: add firmware for bcm4366 device (2016-01-25 15:15:34 -0800)
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 f7996657e8f25386541593242cb8e906d9808ec7:
linux-firmware: intel: Update Skylake audio firmware (2016-02-04 10:36:52 +0530)
----------------------------------------------------------------
Vinod Koul (2):
linux-firmware: intel: add symbolic link and file versions
linux-firmware: intel: Update Skylake audio firmware
WHENCE | 4 ++--
intel/dsp_fw_release.bin | Bin 233472 -> 23 bytes
intel/dsp_fw_release_v827.bin | Bin 0 -> 233472 bytes
intel/dsp_fw_release_v869.bin | Bin 0 -> 233472 bytes
4 files changed, 2 insertions(+), 2 deletions(-)
mode change 100644 => 120000 intel/dsp_fw_release.bin
create mode 100644 intel/dsp_fw_release_v827.bin
create mode 100644 intel/dsp_fw_release_v869.bin
Thanks
--
~Vinod
next reply other threads:[~2016-02-04 5:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 5:12 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-05 6:53 [GIT PULL]: Update sst audio firmware for Skylake Vinod Koul
2016-05-16 19:22 ` Kyle McMartin
2016-03-16 6:44 Vinod Koul
2016-03-19 4:07 ` Kyle McMartin
2016-01-05 13:48 Vinod Koul
2016-01-10 19:38 ` 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=20160204051227.GP11744@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).