From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Jian-Hong Pan <jian-hong@endlessm.com>,
ALSA development <alsa-devel@alsa-project.org>,
sound-open-firmware@alsa-project.org,
Daniel Drake <drake@endlessm.com>
Subject: Re: [Sound-open-firmware] Signed firmware availability for kbl/cnl
Date: Fri, 2 Aug 2019 14:24:00 -0500 [thread overview]
Message-ID: <52e5c627-44c0-146b-2652-0e2790bac74b@linux.intel.com> (raw)
In-Reply-To: <3834d741-906e-1a6b-d6cb-cccb29f98fb4@perex.cz>
>> Would we also use semantic versioning to align the UCM with the
>> topology and FW ? Currently we use semantic versioning for topology and
>> FW.
>
> If we have the versions exported to ther user space, the UCM configuration
> loader / parser can use this information to select or verify the right UCM
> configuration. The semantic versioning in UCM files sounds good to me, too.
My understanding semantic versioning is that it provides means to handle
minor differences where a new capability is ignored in backwards
compatible ways. This is what we use for SOF structures between driver
and firmware, new fields might be added but used or not depending on
versions.
For UCM, the interaction with other layers is limited to stream numbers
and control names, so I am not sure what semantic versioning and
backwards compatibility would mean here? I am all for it, but I don't
get how it would work.
next prev parent reply other threads:[~2019-08-02 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD8Lp45Bp1xVC7NjuNaANA7kAEN2Edshw+cViaTF3tRZEumgZA@mail.gmail.com>
[not found] ` <cc9fa5b52138daffb09dc5b66ea9248379c9f60e.camel@linux.intel.com>
[not found] ` <CAD8Lp46GW8n8K7ttOeSje_au06BsyvCp4seVwj2wNbipei5ssA@mail.gmail.com>
[not found] ` <a4b17a75-d4e0-fc6b-a286-aa6b7b281b7d@linux.intel.com>
[not found] ` <CAD8Lp444soO1i8mWF73eucT16yAhy2js1byWJCTV5fn=TikHBg@mail.gmail.com>
[not found] ` <9e8b667f1aa2333dbcc34b5253372d1a8667551e.camel@linux.intel.com>
[not found] ` <ee34f820-0753-dfbe-09c0-7147cf229cc0@perex.cz>
[not found] ` <6493f195-eb5a-1a6d-2c31-e3a4123b2ad1@linux.intel.com>
[not found] ` <7c940d90-297e-19c0-2f74-1843439d5ccf@perex.cz>
[not found] ` <d41b02286db2a827648d1c1ec793bbd0a55e99c1.camel@linux.intel.com>
2019-07-24 16:23 ` [Sound-open-firmware] Signed firmware availability for kbl/cnl Jaroslav Kysela
2019-07-31 13:23 ` Liam Girdwood
2019-07-31 14:01 ` Pierre-Louis Bossart
2019-07-31 14:07 ` Liam Girdwood
2019-07-31 17:52 ` Jaroslav Kysela
2019-07-31 17:29 ` Jaroslav Kysela
2019-07-31 18:14 ` Pierre-Louis Bossart
2019-08-02 8:21 ` Jaroslav Kysela
2019-08-02 14:40 ` Liam Girdwood
2019-08-02 19:01 ` Jaroslav Kysela
2019-08-02 19:24 ` Pierre-Louis Bossart [this message]
2019-08-05 14:39 ` Liam Girdwood
2019-08-05 14:36 ` Liam Girdwood
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=52e5c627-44c0-146b-2652-0e2790bac74b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=drake@endlessm.com \
--cc=jian-hong@endlessm.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=perex@perex.cz \
--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 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.