-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Reintroduce tfm-mcuboot #30614
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
Reintroduce tfm-mcuboot #30614
Conversation
ed2bec5 to
9c4b2d4
Compare
|
The following projects have a revision update in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
west.yml
Outdated
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.
We should not import from Zephyr modules from Zephyr manifest.
Please revert to the code you initially had when using Zephyr mcuboot, like you had here:
b34978f
- name: tfm-mcuboot
path: modules/tee/tfm/mcuboot
repo-path: mcuboot
revision: 1.7.0-rc1
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.
As mentioned in Slack, I also agree with @tejlmand. We agreed that zephyr-specific changes and glue should stay in the main zephyr tree, and this is very much that in my opinion.
9c4b2d4 to
14d4fd6
Compare
14d4fd6 to
8f6d9a9
Compare
Turn on import, so tfm's west.yml is processed. Signed-off-by: Øyvind Rønningstad <[email protected]>
8f6d9a9 to
2cd39b2
Compare
|
Added comment, updated sha, and changed from |
|
@galak are you OK with this? |
Reintroduce #30050, reverted in #30610Note that because of #30616, this now correctly runs the doc build, which passes with the addition of thewest updateline.Moved west.yml entry from module to zephyr's west.yml