From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: "sound-open-firmware@alsa-project.org"
<sound-open-firmware@alsa-project.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: SOF 1.1 Release
Date: Thu, 05 Apr 2018 10:42:42 +0100 [thread overview]
Message-ID: <1522921362.1923.958.camel@linux.intel.com> (raw)
Sound Open Firmware 1.1 has now been released and available here :-
git://git.alsa-project.org/sound-open-firmware.git
git://git.alsa-project.org/sound-open-firmware-tools.git
Significant changes since 1.0 :-
o Support for Playback/Capture on Intel Apollolake and Cannonlake platforms.
o Initial support for Intel Haswell and Broadwell platforms.
o Support for DMA based firmware tracing to host userspace.
o SIMD optimisations for SRC on xtensa ISA.
o Initial support for running firmware components on host.
Plans for 1.2 :-
o Playback/Capture on Haswell/Broadwell.
o SIMD optimisations for volume and mixer.
o Improved host based component testing.
o Initial runtime module support.
SOF Linux driver dependencies for ALSA/ASoC have also started to upstream.
Driver patches will continue to flow in anticipation for base SOF driver in
4.18.
Thanks
Liam
reply other threads:[~2018-04-05 9:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1522921362.1923.958.camel@linux.intel.com \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=sound-open-firmware@alsa-project.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