alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, liam.r.girdwood@linux.intel.com,
	alsa-devel@alsa-project.org, vkoul@kernel.org
Subject: Re: [PATCH] ASoC: Intel: common: rename 'reef' to 'sof' in ACPI matching table
Date: Wed, 20 Jun 2018 10:59:43 -0500	[thread overview]
Message-ID: <f1690317-8d6e-7877-b813-3c324f92d311@linux.intel.com> (raw)
In-Reply-To: <20180620111736.GD6242@sirena.org.uk>

On 6/20/18 6:17 AM, Mark Brown wrote:
> On Tue, Jun 19, 2018 at 02:00:37PM -0500, Pierre-Louis Bossart wrote:
> 
>> -	.sof_fw_filename = "intel/reef-byt.ri",
>> -	.sof_tplg_filename = "intel/reef-byt-rt5670.tplg",
>> +	.sof_fw_filename = "intel/sof-byt.ri",
>> +	.sof_tplg_filename = "intel/sof-byt-rt5670.tplg",
> 
> We're sure nobody is using this stuff in production yet?

Yes. The topology tools were changed back in April to remove all 
references to reef, same for the firmware code.

https://github.com/thesofproject/soft/commit/4f6d459586c22a8c9d946ee821ccf9c1ce7804c7

we will make sure the IPC and topology are tracked in backwards 
compatible ways once devices are released, it's on our TODO list to add 
checks for version numbers and always make sure the kernel update does 
not require changes to the firmware or filesystems.

  reply	other threads:[~2018-06-20 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 19:00 [PATCH] ASoC: Intel: common: rename 'reef' to 'sof' in ACPI matching table Pierre-Louis Bossart
2018-06-20 11:17 ` Mark Brown
2018-06-20 15:59   ` Pierre-Louis Bossart [this message]
2018-06-21 15:31 ` Applied "ASoC: Intel: common: rename 'reef' to 'sof' in ACPI matching table" to the asoc tree Mark Brown

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=f1690317-8d6e-7877-b813-3c324f92d311@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).