From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Bernie Innocenti <bernie@codewiz.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] [PATCH 2/3] ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names.
Date: Thu, 2 Jan 2020 12:00:58 -0600 [thread overview]
Message-ID: <f2c43959-aa1f-6136-f387-e4f44c2f889d@linux.intel.com> (raw)
In-Reply-To: <1ae8f294-a6c7-d104-8e57-a86cf5b9b07c@codewiz.org>
On 12/29/19 6:15 PM, Bernie Innocenti wrote:
> Greetings Liam and Pierre,
>
> > @@ -149,7 +149,7 @@ static const struct sof_dev_desc cml_desc = {
> > .chip_info = &cnl_chip_info,
> > .default_fw_path = "intel/sof",
> > .default_tplg_path = "intel/sof-tplg",
> >- .nocodec_fw_filename = "sof-cnl.ri",
> >+ .nocodec_fw_filename = "sof-cml.ri",
>
> Where is this new firmware file? This patch has flown into Fedora
> kernels 5.4.5-301.fc31 and 5.5.0-0.rc3.git0.1.fc32, and now I'm getting
> this error when the module loads on a Thinkpad X1 Gen 7:
>
> sof-audio-pci 0000:00:1f.3: Direct firmware load for
> intel/sof/sof-cml.ri failed with error -2
>
> The other .ri files come with alsa-firmware, but sof-cml.ri is absent in
> the latest upstream release (alsa-firmware-1.2.1).
>
> The only reference I could find is this symlink, but it's not clear to
> me how and when it will get into distributions:
>
>
> https://github.com/thesofproject/linux-firmware/commit/beff732e6642bd77dac5dd08514264f055fc4d10#diff-76c141712563cc9d4730eb63acb36ad5R3807-R3808
Yes, sorry for the delay. we run out of time at the end of 2019 (needed
to verify the compilation of the firmware signed with the community key
and matching changes in the SOF driver to select the right files [1]).
Once this is done, we will make a pull request so that the releases flow
into linux-firmware.
[1] https://github.com/thesofproject/linux/pull/1646
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-01-02 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 0:15 [alsa-devel] [PATCH 2/3] ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names Bernie Innocenti
2020-01-02 18:00 ` Pierre-Louis Bossart [this message]
2020-01-04 10:15 ` Jaroslav Kysela
-- strict thread matches above, loose matches on Subject: below --
2019-11-11 22:28 [alsa-devel] [PATCH 0/3] ASoC: Intel/SOF: split CFL, CNL, CML firmware names Pierre-Louis Bossart
2019-11-11 22:29 ` [alsa-devel] [PATCH 2/3] ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names Pierre-Louis Bossart
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=f2c43959-aa1f-6136-f387-e4f44c2f889d@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bernie@codewiz.org \
--cc=liam.r.girdwood@linux.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).