fix version of trusted-firmware-a #69
Open
Conversation
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
|
thanks for the patch, I'll review it shortly for inclusion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When building with
XILINX_RELEASE_VERSIONset tov2024.2, a wrong version of thetrusted-firmware-acomponent is used (the latestv2025.1). There are two reasons for this:XILINX_ATF_VERSIONstring contains only major and minor SemVer numbers. The filenames inmeta-xilinx-core/recipes-bsp/trusted-firmware-aalso have the patch component.PREFERRED_VERSIONforvirtual/arm-trusted-firmwarehas no effect.trusted-firmware-ais only built with version2024.2when it is explicitly specified without the virtual indirect.