-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to YEAR.MONTH[.MINOR] based versioning for sof-bin #134
Comments
FYI @thesofproject/maintainers |
You are proposing opposite. You just clarify the release date in the package name. But I see that this follows the linux firmware releases. Fedora does not have version in the file tree (because the information was duplicate - package name + directory name) and multiple symlink levels is ugly for the standard distribution). Source example:
Fedora alsa-sof-firmware-2.2.5-1.fc38.noarch:
I will probably create a file in /usr/share/doc/alsa-sof-firmware/ tree with the file -> SOF version mapping. |
Ack @perexg , the names will not be overlapping so install without versions and symlinks is possible. We plan to use same scripting in sof-bin git we used with 2.2.6 to make the tarball, so that e.g. we include a manifest file into the package that specifies versions for all binary files (see https://github.com/thesofproject/sof-bin/releases/download/v2.2.6/sof-bin-v2.2.6.tar.gz and the manifest.txt it has). |
I tried to negate the sentence you quoted but I couldn't find how :-)
Adding the date is not the important change. The important change is removing the misleading "v2.6" when the package content is actually a mix of v2.6 and v2.2.2 content (depending on the hardware generation).
This was a design mistake in
And in the future:
|
The manifest.txt looks good. I'll include it to the doc directory in next release.
Yep, it seems less work for Fedora package script. |
As discussed in: - thesofproject#134 - thesofproject#133 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Fix submitted in #136, please review. Even if you don't have time to review the code, please take a quick look at how the change in the sample test tree. |
As discussed in: - thesofproject#134 - thesofproject#133 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Draft release tarball for sof-bin-v2023.09-rc1 is now available at: |
And pre-release tagged and published at https://github.com/thesofproject/sof-bin/releases/tag/v2023.09-rc1 Feedback is welcome. We'll follow same structure for the final v2023.09 release. |
Tried the pre-release tarball. LGTM, thanks! |
Probably the wrong place to flag this, and maybe I'm missing something obvious, but were the MTL binaries missed from the new release? I'm not seeing mtl.ri in there. |
They're present:
|
Oh...got it. They moved under ipc4. My bad...sorry! (scuttling back under rock) |
@kv2019i eventually got tired of me complaining and very recently documented all this here: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html#firmware-binary https://github.com/thesofproject/sof-docs/pull/475/files
|
New test code submitted in (one more coming after this one) |
Second and last |
All merged. |
Just as an info note - I tweaked my Debian package stuff to work with the new format and it's all looking good. Testing it on a few platforms now, so far no issues. |
This sort of feedback (good or bad!) is extremely useful to us, please keep it coming. |
Problem statement
Since SOF v2.2, sof-bin packaging has supported inclusion of firmware and topology files from multiple source revisions of SOF.
The motivation for this is to allow a single sof-bin release to all necessary firmware and topology files, for all targets supported by upstream SOF binary releases.
Note: the upstream sof-bin releases do not cover all vendors -- binaries are also distributed via OEM and other channels.
What is changing for SOF v2.7
To clarify the relation of sof-bin release to a SOF firmware versions, sof-bin releases will move to a YEAR.MONTH[.MINOR] versioning.
The first new-style release will be sof-bin-2023.09. Current submitted binaries will include Intel binaries based on SOF2.2 (for Intel Raptor Lake and older platforms) and the soon to be released SOF2.7 (for newer Intel platforms). The release is open to other vendors to submit their binaries for upstream distribution.
Package content is not going to change and distribution packages can copy the release contents verbatim to /lib/firmware (as has been done in previous sof-bin packages).
Timeline
Synrhonized with SOF2.7 released timeline thesofproject/sof#8017
In future, sof-bin releases will be done in sync with the SOF releases (current cadence is a quarterly release).
The text was updated successfully, but these errors were encountered: