-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
WIP/Draft: KGPE-D16 re-support #1634
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Thomas Clarke <[email protected]>
credit: Thierry Laurion (tlaurion) linuxboot@842eda2#diff-18936189b28399cf48703d0c1ec1df33e57c559de2a12f4438be00e6813bdb68 Signed-off-by: Thomas Clarke <[email protected]>
Signed-off-by: Thomas Clarke <[email protected]>
Signed-off-by: Thomas Clarke <[email protected]>
Signed-off-by: Thomas Clarke <[email protected]>
d7677f3
to
6642b2d
Compare
@Tonux599 on tpm support, boards need to be either TPM1 or tpm2 since toolstack is different. You can look at qemu boards for examples |
ELI5? State Of the Art? |
@Tonux599 ref of vikings HCL over 4.11 and changes from dasharo and or regressions/improvements |
Define SoA? But I'm not too sure to be honest, I've heard that Dasharo is slower at runtime. Once my testing suit is setup I'll run some benchmarks and try and reproduce. |
SoA: State Of the Art. EDIT: #1760 merged since no regression observed on a previously working system and should improve situation where previously unstable. |
Expect 6ish months to complete due to other commitments.
Primary work/testing will be on the
kgpe-d16_workstation
variant but other can be re-enabled if others want to test them.Todo List:
Either support TPM1.2 and TPM2.0 on the same board config. Else,setup multiple variants for TPM1.2 and TPM2.0.