summaryrefslogtreecommitdiffstats
path: root/IntelFsp2Pkg
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2024-09-03 09:58:49 +0200
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2024-09-03 22:47:09 +0000
commitafba5358c816c88f2b202a45c31fe80e34dd9368 (patch)
tree98c874e0022be7d6dcfce71115feff4f2072d49d /IntelFsp2Pkg
parent8504d2be17c98265049ec334711aad4c0baed1d7 (diff)
downloadedk2-afba5358c816c88f2b202a45c31fe80e34dd9368.tar.gz
edk2-afba5358c816c88f2b202a45c31fe80e34dd9368.tar.bz2
edk2-afba5358c816c88f2b202a45c31fe80e34dd9368.zip
ArmVirtPkg: Resolve RngLib via RngDxe for TRNG support
Gerd reports that ArmVirtQemu running under KVM lost network boot support on systems that do not implement the RNDR/RNDRRS system registers, which provide an architectural, CPU-based source of random numbers. Under KVM, the TRNG SMCCC is available as a fallback, which is exposed via RngDxe but not via the base RngLib library. This means that direct users of RngLib, such as OpensslLib, have no access to the TRNG based entropy source. Let's fix this by resolving RngLib dependencies for UEFI_DRIVER type drivers via DxeRngLib, which uses the protocol exposed by RngDxe internally. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'IntelFsp2Pkg')
0 files changed, 0 insertions, 0 deletions