Skip to content

Conversation

@ktrzcinx
Copy link
Member

Introduced changes add extended manifest at the begin of firmware
image, as a firmware metadata description.

Signed-off-by: Karol Trzcinski karolx.trzcinski@linux.intel.com

This PR shouldn't be merged before a flag day.
Added as PR to make it easy to cherry-pick for development purposes.

@ktrzcinx ktrzcinx requested a review from jajanusz as a code owner May 20, 2020 06:41
@keyonjie
Copy link
Contributor

shall we bump the major version for this also?

@ktrzcinx
Copy link
Member Author

@keyonjie major abi number should be untouched, moreover this patch is going to hang for a long time.

@keyonjie
Copy link
Contributor

@keyonjie major abi number should be untouched, moreover this patch is going to hang for a long time.

Can you add prefix like [DO NOT MERGE] to the PR subject, otherwise it could be merged by mistake sometimes.

And remove the prefix once it is time for merging it.

@ktrzcinx ktrzcinx changed the title ext_manifest: Use ext manifest by default in output image [DO NOT MERGE] ext_manifest: Use ext manifest by default in output image May 20, 2020
@ktrzcinx ktrzcinx requested a review from xiulipan as a code owner May 20, 2020 09:50
Add extended manifest at the begin of firmware image,
as a firmware metadata description.

Signed-off-by: Karol Trzcinski <karolx.trzcinski@linux.intel.com>
@ktrzcinx
Copy link
Member Author

@lgirdwood @plbossart @kv2019i @lyakh, is it right time, after v1.6 release, to merge this PR and include extended_manifest to each firmware image by default?

@kv2019i
Copy link
Collaborator

kv2019i commented Sep 30, 2020

@ktrzcinx wrote:

@lgirdwood @plbossart @kv2019i @lyakh, is it right time, after v1.6 release, to merge this PR and include extended_manifest to each firmware image by default?

Yes please! Ext-manifest should be enabled for all V1.7 binaries, so to get maximum testing coverage, we should change the default as soon as possible after 1.6 is done and the "merge window" for V1.7 opens. In kernel, ext-manifest support is in v5.8 and newer kernels and by the time we release 1.7, 5.10 is probably out.

@ktrzcinx ktrzcinx changed the title [DO NOT MERGE] ext_manifest: Use ext manifest by default in output image ext_manifest: Use ext manifest by default in output image Oct 1, 2020
@lgirdwood
Copy link
Member

@kv2019i just to clarify - is kernel ready if we merge this now ? v1.6 is now on a stable branch.

@wwittbrx
Copy link
Contributor

wwittbrx commented Oct 1, 2020

@lgirdwood Please hold off with merging this PR, there is a TGL load error in smoke tests that needs to be resolved first. I will investigate as soon as possible and get back to you.

@kv2019i
Copy link
Collaborator

kv2019i commented Oct 1, 2020

@lgirdwood wrote:

@kv2019i just to clarify - is kernel ready if we merge this now ? v1.6 is now on a stable branch.

Well that's the thing. It was ready many months ago, but as this has not been tested by anyone and has been disabled in FW builds, nobody has been testing this. But yes, support is there in place, so if CI is good, go ahead and merge. The sooner we discover any lurking issues, the better.

@wwittbrx
Copy link
Contributor

wwittbrx commented Oct 2, 2020

@lgirdwood CI issues have been resolved, and the PR is good to merge from my perspective.

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.

5 participants