-
Notifications
You must be signed in to change notification settings - Fork 321
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
rimage: module: Fix section order in output image #8401
Conversation
@saisurya-ch can you verify? |
@softwarecki can you explain why this didn't affect Intel? Because we don't use a "simple" (?) manifest? |
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.
.ri file is written in the correct order as required.
This would be ready to go, but we need a clean run of the mandatory CI checks. @softwarecki can you check? |
9692aae
to
483053d
Compare
It appears that Intel platforms use functions from the |
@kv2019i , @lgirdwood , based on @softwarecki's description of |
Not impacting v2.7.1, but can be added to v2.7.2 if we need to. |
483053d
to
df3af2b
Compare
Fixed the order in which sections are placed in the output firmware image for platforms using a simple manifest. Fixes: thesofproject#8336 Signed-off-by: Adrian Warecki <[email protected]>
df3af2b
to
d39f3b4
Compare
@wszypelt @softwarecki The fails look unrelated to this PR, can you take a lot or give go-ahead to merge as this is urgent for non-Intel configurations. |
all green in Internal Intel CI System :) |
Fixed the order in which sections are placed in the output firmware image for platforms using a simple manifest.
Fixes: #8336