Open
Conversation
micgor32
added
enhancement
micgor32
force-pushed
the
cbnt21-refactor
branch
from
b32bd3c to
721fccd
Compare
Contributor
Author
|
force pushed to amend previous commit message :D |
micgor32
force-pushed
the
cbnt21-refactor
branch
from
a66a1f1 to
1b126fe
Compare
Contributor
Author
|
squashed fixup commits |
micgor32
force-pushed
the
cbnt21-refactor
branch
from
1b126fe to
e096604
Compare
micgor32
requested review from
ArthurHeymans,
ChriMarMe,
PatrickRudolph,
walterchris and
zaolin
as code owners
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Fiano has now one package for all three BG/CBnT specifications. Versions are determined by the type constructor based on the BG version provided. Similar story for BPM and KM packages. Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
…d KM Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Some runtime tests give representative results if ran on particular CBnT version (will be documented in TESTPLAN.md in the follow up commits). We can not assume version based on header version in the image as with static tests, as there is nothing stopping the user from using different fw image than the one on the running system. What we can do instead, is to use CPUID to retrieve Display Model and compare it to the list of known microachitecture acronyms, and based on that determine the CBnT version. Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
`fit` package in Fiano now uses the actual firmware image size instead of assuming it fills out the whole SPI chip from which it was read off. Thus the fit's api changed a bit, and we have to also pass fw size. Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
…in VersionedData Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
…tion Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
…ified pkgs Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
Signed-off-by: Michal Gorlas <michal.gorlas@9elements.com>
micgor32
force-pushed
the
cbnt21-refactor
branch
from
05f65a1 to
acf1084
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for CBnT 2.1 (MTL and newer generations) and adapts to Fiano
intel/metadatabreaking changes.Short summary of changes:
bgandcbntpackages: also implies that KM and BPM are no longer versioned. Because of the unification, the constructors for the Manifests do the job of returning the correct implementation of either KM or BPM based on the BtG/CBnT version provided. This also implies that we have to make type assertions in few places.cmd/core/bg-suite/TESTPLAN.md. Because some runtime tests (5, 6 and 8) are only valid on either 1.0/2.0 or 2.1, add the logic for determining the BtG/CBnT version on runtme.Note: WIP till Fiano changes are upstreamed, the branch can be, however tested in the meantime after setting the replacement in go.mod: