public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Paul Dann <pdgiddie@gmail.com>,
	ALSA development <alsa-devel@alsa-project.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>
Subject: Re: SOF 1.5 release on FTP server
Date: Mon, 8 Jun 2020 08:28:08 -0500	[thread overview]
Message-ID: <3fea0c1d-9e85-2d84-d7bd-4e07a7d3496b@linux.intel.com> (raw)
In-Reply-To: <CALZj-VoJ0tMNyD6aZyLdBWYD3meWaqKjo-1wQww0wk1En2nqwQ@mail.gmail.com>



On 6/7/20 3:13 PM, Paul Dann wrote:
> On Mon, 1 Jun 2020 at 15:45, Kai Vehmanen <kai.vehmanen@linux.intel.com> wrote:
>> Paul, I can confirm the sof-bin is the definitive location to get
>> the SOF binaries.
> 
> Many thanks both for confirming the new source. I notice that the old
> FTP package contains the following .ri and .ldc files that are not
> present in the new Github repo:

It's a clean-up indeed.

> sof-hsw

No longer supported (and no commercial platforms known to use the DSP)

> sof-imx8

This would need to be provided by NXP. Each company is responsible for 
providing the firmware for their platforms.

> sof-jsl

Not fully supported upstream, but indeed we need to check this one. Liam?

> sof-kbl
> sof-skl

Not supported.

> sof-sue

I don't think this was ever supported outside of Intel

> I'd just like to double-check that shipping the new package without
> these files won't lead to reduced functionality?

we'll check this JSL (JasperLake) firmware but for existing platforms 
this looks fine.

      reply	other threads:[~2020-06-08 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  7:24 SOF 1.5 release on FTP server Paul Dann
2020-06-01  7:53 ` Jaroslav Kysela
     [not found]   ` <CALZj-VoLtoNbPZ1evLYqTxEg7XaTiEjgdB+WLE7duLfxF2ohLA@mail.gmail.com>
2020-06-01  9:23     ` Jaroslav Kysela
2020-06-01 14:45       ` Kai Vehmanen
2020-06-07 20:13         ` Paul Dann
2020-06-08 13:28           ` Pierre-Louis Bossart [this message]

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=3fea0c1d-9e85-2d84-d7bd-4e07a7d3496b@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pdgiddie@gmail.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