Skip to content
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

Add sof-v2.9 for Intel hardware #164

Merged
merged 5 commits into from
Apr 2, 2024

Conversation

kv2019i
Copy link
Collaborator

@kv2019i kv2019i commented Mar 26, 2024

No description provided.

@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 27, 2024

V2 uploaded, now tests pass.

@kv2019i kv2019i requested a review from lyakh March 27, 2024 15:09
@kv2019i kv2019i force-pushed the 202403-sof29-community branch from bf00d93 to 559970b Compare March 27, 2024 19:11
@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 27, 2024

V3: fix tarball_multi_releases

  • but BATS tests are failing

V4: fix BATS tests again

@kv2019i kv2019i force-pushed the 202403-sof29-community branch from 559970b to 99ca1e7 Compare March 27, 2024 19:43
@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 27, 2024

V5: one more fixup to the sof-ace-tplg symlink handling

Copy link
Collaborator

@ujfalusi ujfalusi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kv2019i, nice and clean, thank you!

@kv2019i kv2019i force-pushed the 202403-sof29-community branch from 99ca1e7 to 2296aba Compare March 28, 2024 11:29
@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 28, 2024

The community binaries have "v2.9-rc1" tag (it's the same commit as v2.9 tag), causing difference in binaries. We really should get rid of this in SOF main.

@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 28, 2024

V6:

  • updated the communiy-signed binaries (now binary uses "v2.9" tag instead of "v2.9-rc1" so there's more obvious match of binaries... both tags point to same git commit so the compiled code is identical, but as the literals are of different size, running a binary diff will show lot of diffences -> now fixed)

Copy link
Collaborator

@marc-hb marc-hb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated the communiy-signed binaries (now binary uses "v2.9" tag instead of "v2.9-rc1" so there's more obvious match of binaries...

Why keep the v2.9-rc1 binaries ?

# the compatibility note for Intel MTL in
# https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html#user-space-and-filesystem-requirements
( cd "${archive_name}"
if test -e "sof-ipc4-tplg-WIP" -a ! -e "sof-ace-tplg-WIP" ; then
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shellcheck would likely say:

Suggested change
if test -e "sof-ipc4-tplg-WIP" -a ! -e "sof-ace-tplg-WIP" ; then
if test -e "sof-ipc4-tplg-WIP" && ! test -e "sof-ace-tplg-WIP" ; then

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marc-hb Hmm, shellcheck seems happy with original.

tests/tests.bats Outdated
diff -qr "$EXTR_REFS"/sof-bin-"$ver" "$(pwd)/sof-bin-$ver"/
# install.sh was updated in 2024.03, so it won't match
# anymore
diff -qr --exclude="install.sh" "$EXTR_REFS"/sof-bin-"$ver" "$(pwd)/sof-bin-$ver"/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please try this instead?

git show v2023.12.1:install.sh > "$(pwd)/sof-bin-$ver"/install.sh

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was there any tools change between v2.8 and v2.9? If not, can you just re-use tools-v2.8 and reduce noice?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marc-hb There was a minor change in sof-ctl, so we need to update.

kv2019i added 5 commits April 2, 2024 12:34
Add binaries for supported Intel systems.

Community binaries build identification "Build #3513".

Also contains topology2/IPC4 topology files for all configurations
supported in the release.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Add support for new sof-ipc4-tplg directory as documented
in updated SOF user-space and filesystem requirements.

Link: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html#user-space-and-filesystem-requirements
Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
The install.sh has been updated to include more directories,
so recreating 2023.09 will cause a mismatch in installed install.sh.
Exclude the known difference in the test case.

Suggested-by: Marc Herbert <marc.herbert@intel.com>
Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
…link

Not ideal, but it seems adding a special case rule is easier to
understand and maintain than trying to modify the existing FW/tplg
copy rules to handle this special case.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Add signed Intel binaries for v2.9 SOF release. Intel
build identification 13778510.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
@kv2019i kv2019i force-pushed the 202403-sof29-community branch from d2ea2ef to 1edb6ca Compare April 2, 2024 11:47
@kv2019i
Copy link
Collaborator Author

kv2019i commented Apr 2, 2024

V7:

  • addressed Marc's comment in test code
  • remove the rc1 community binaries from git history
  • no changes to FW binaries or topologies

@marc-hb please check

@kv2019i kv2019i merged commit 390fd08 into thesofproject:main Apr 2, 2024
2 checks passed
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.

4 participants