[WIP]: envconfig: Add support for secure operation system #9386
Conversation
This file contains 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
There are many secure operation systems likes optee from linaro, trusty from Google, and many SoC vendor has its own proprietary one. They don't really share many APIs, we could build trusted application with meson as long as you prepare a proper staging sysroot and correct cross properties.
hizukiayaka
force-pushed
the
fixup_tee
branch
from
01aacff to
12d37f7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are many secure operation systems likes optee from linaro, trusty from Google, and many SoC vendor has its own proprietary one.
They don't really share many APIs, we could build trusted application with meson as long as you prepare a proper
staging sysroot and correct cross properties.
We need a cross file for host to build the client agent part and another cross file for teeos to build TA. So currently I need to run meson twice. In some case, they would have to same the same top directory, without this patch I would not know I am building the CA or TA.