Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only builds for one target, can we make it target generic. @marc-hb any suggestions how how this would be done here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marc-hb Except for adding CONFIG_IPC_MAJOR_4=y here,
according to @RanderWang,CONFIG_RIMAGE_SIGNING_SCHEMA need to be modified from "tgl-h" to "tgl-cavs" too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But still encountered DSP topology loading failure with this fw and innersource topic sof cavs dev kernel.
Will post an issue later
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I missed this.
We can't do it like this because this pollutes the
git diffand it will also keep growing the .conf file in people's workspaces.Zephyr has a number of Kconfig options:
https://docs.zephyrproject.org/2.7.0/guides/build/kconfig/setting.html#the-initial-configuration
For more inspiration there's also https://github.com/thesofproject/kconfig
cc:
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The document doesn't mention application level kconfig overriding, but according to
we can workaround it by caching a
<BOARD>_<revision>.conf, and copy it to zephyr tree when build SOF+Zephyr+IPC4. @XiaoyunWu6666 can you try this?