[PATCH] bli: set LoaderTpm2ActivePcrBanks runtime variable

2025-07-18 Thread luca . boccassi
From: Luca Boccassi It turns out checking from userspace is not 100% reliable to figure out whether the firmware had TPM2 support enabled or not. For example with EDK2 arm64, the default upstream build config bundles TPM2 support with SecureBoot support, so if the latter is disabled, TPM2 is

[PATCH] bli: set LoaderTpm2ActivePcrBanks runtime variable

2025-07-18 Thread luca . boccassi
From: Luca Boccassi It turns out checking from userspace is not 100% reliable to figure out whether the firmware had TPM2 support enabled or not. For example with EDK2 arm64, the default upstream build config bundles TPM2 support with SecureBoot support, so if the latter is disabled, TPM2 is

Re: [PATCH] bli: set LoaderTpm2ActivePcrBanks runtime variable

2025-07-25 Thread Luca Boccassi
On Fri, 25 Jul 2025 at 14:38, Daniel Kiper wrote: > > On Fri, Jul 18, 2025 at 11:46:52PM +0100, luca.bocca...@gmail.com wrote: > > From: Luca Boccassi > > > > It turns out checking from userspace is not 100% reliable to figure out > > whether > > the firm

[PATCH v2] bli: set LoaderTpm2ActivePcrBanks runtime variable

2025-07-25 Thread luca . boccassi
From: Luca Boccassi It turns out checking from userspace is not 100% reliable to figure out whether the firmware had TPM2 support enabled or not. For example with EDK2 arm64, the default upstream build config bundles TPM2 support with SecureBoot support, so if the latter is disabled, TPM2 is