From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Curtis Malainey <cujomalainey@google.com>,
ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Amadeusz SX2awiX4ski <amadeuszx.slawinski@linux.intel.com>
Subject: Re: [PATCH] ALSA: core - add more card sysfs entries
Date: Fri, 9 Apr 2021 13:55:58 -0500 [thread overview]
Message-ID: <eff846c0-c141-8fd2-bad1-dfd128dad58a@linux.intel.com> (raw)
In-Reply-To: <s5ho8en4dn7.wl-tiwai@suse.de>
>> No, replacing firmware files is not viable.
>>
>> Let me give you a practical example. In the course of SOF development,
>> we routinely copy new test firmware+topology in the location of
>> distribution-managed files. It's classic that when there is a
>> distribution update in the background to install the latest SOF
>> release, our test files are overwritten and it's not usual for
>> developers to lose time trying to figure out why the functionality
>> changed. We do need to have multiple paths and NEVER override what is
>> provided by the distributions. it's the moral equivalent of /usr/bin
>> v. /usr/local/bin.
>
> Use /lib/firmware/updates/*. That precedes over the standard path
> /lib/firmware/*. (Also /lib/firmware/updates/$VERSION has even higher
> priority.)
thanks for the feedback Takashi, I had no idea this even existed :-)
The documentation is here:
https://www.kernel.org/doc/html/latest/driver-api/firmware/fw_search_path.html
I guess that removes the need for udev rules to select the
firmware+topology in simple cases, e.g. if you have only one custom
version or an image overlay.
next prev parent reply other threads:[~2021-04-09 18:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 9:43 [PATCH] ALSA: core - add more card sysfs entries Jaroslav Kysela
2021-04-08 10:38 ` Takashi Sakamoto
2021-04-08 11:05 ` Takashi Iwai
2021-04-08 11:21 ` Jaroslav Kysela
2021-04-08 12:05 ` Mark Brown
2021-04-08 13:18 ` Takashi Iwai
2021-04-08 14:12 ` Pierre-Louis Bossart
2021-04-08 14:47 ` Mark Brown
2021-04-08 15:04 ` Jaroslav Kysela
2021-04-08 15:11 ` Amadeusz Sławiński
2021-04-08 15:01 ` Jaroslav Kysela
2021-04-08 15:32 ` Pierre-Louis Bossart
2021-04-08 16:53 ` Jaroslav Kysela
2021-04-08 18:51 ` Pierre-Louis Bossart
2021-04-08 19:25 ` Jaroslav Kysela
2021-04-08 19:41 ` Pierre-Louis Bossart
2021-04-08 19:56 ` Curtis Malainey
2021-04-08 20:01 ` Jaroslav Kysela
2021-04-09 16:43 ` Jaroslav Kysela
2021-04-09 7:39 ` Takashi Iwai
2021-04-09 8:34 ` Jaroslav Kysela
2021-04-09 8:55 ` Takashi Iwai
2021-04-09 9:09 ` Amadeusz Sławiński
2021-04-09 13:54 ` Jaroslav Kysela
2021-04-09 15:55 ` Pierre-Louis Bossart
2021-04-09 16:38 ` Takashi Iwai
2021-04-09 18:55 ` Pierre-Louis Bossart [this message]
2021-04-09 16:39 ` Mark Brown
2021-04-08 16:22 ` Mark Brown
2021-04-08 16:50 ` Pierre-Louis Bossart
2021-04-08 18:20 ` Mark Brown
2021-04-08 17:20 ` Jaroslav Kysela
2021-04-08 17:47 ` Mark Brown
2021-04-08 11:25 ` Jaroslav Kysela
2021-04-10 19:11 ` Jaroslav Kysela
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=eff846c0-c141-8fd2-bad1-dfd128dad58a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.