Skip to content

Add mtl-s to v2.15.1 and a signing-key continuity check - #210

Closed
lgirdwood wants to merge 4 commits into
thesofproject:mainfrom
lgirdwood:add-v2.15.1-mtl-s-signing-key-check
Closed

lgirdwood wants to merge 4 commits into
thesofproject:mainfrom
lgirdwood:add-v2.15.1-mtl-s-signing-key-check

Conversation

@lgirdwood

Copy link
Copy Markdown
Member

Summary

  • Add the v2.15.1 point-release signed firmware binary for Intel Meteor Lake S (mtl-s), following the v2.14.1 point-release precedent.
  • Alias arl-s's intel-signed firmware to mtl-s (same ACE 1.5 DSP, same relationship as the existing arl -> mtl symlink), filling the arl-s intel-signed slot that's been empty since v2.15.
  • Fix a sha256sum --check portability issue in tarball_multi_releases.bash's checksum verification (some coreutils implementations reject our tab-separated checksum file format); verify each entry directly instead.
  • Add a signing-key continuity check to validate_sof_install.py: extracts a sha256 fingerprint of each signed .ri/.llext file's CSS manifest RSA modulus (both locally and in the remote/SSH manifest script), and adds --compare-signing-keys PREV_DIR CURR_DIR to diff signing-key identity between two version directories. Wired into a new tests/key_continuity.bats that dynamically discovers every consecutive point-release pair, and a dedicated .github/workflows/key-continuity.yml.

Test plan

  • bats tests/*.bats — all 21 tests pass, including the new signing key continuity tests
  • --compare-signing-keys correctly flags a known historical key rotation (legacy jsl v1.9 -> v1.9.2) and exits 1
  • --compare-signing-keys v2.15 v2.15.1 passes with mtl-s/arl-s reported as new-in-release (informational), exit 0
  • compare_signed_unsigned.py reports arl-s as matching mtl-s at the module level
  • shellcheck -e SC3043 clean on the new bats file and the existing glob

🤖 Generated with Claude Code

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants