SBSA Reference Platform in QEMU uses Neoverse-N2 cpu by default now. This core supports FEAT_RNG feature so I thought that it should be possible to use it for EFI_RNG_PROTOCOL.
Checked history and found that commit 5de5e230a80bed083360da95ba16a2c4a001620d (in EDK2) enabled that for ArmVirt platform. When I boot with Neoverse-N2 or 'max' cpu then EFI_RNG_PROTOCOL gets reported by 'efi-stub' on Linux boot. Other cpu models do not have FEAT_RNG so RngDxe driver is not running and we have situation similar to previous one - no EFI_RNG_PROTOCOL reported. I left ArmTrngLib enabled because RngDxe does not start without it. Probably there is a better way to handle it. Now the question is: do we want to go this way? And what to do with older cores? BaseRngLibTimerLib is not(?) used now so are they left with nothing? I would prefer to not add 'virtio-rng-pci' device in QEMU to have some TRNG emulated. Signed-off-by: Marcin Juszkiewicz <marcin.juszkiew...@linaro.org> Marcin Juszkiewicz (1): SbsaQemu: use FEAT_RNG for EFI_RNG_PROTOCOL Platform/Qemu/SbsaQemu/SbsaQemu.dsc | 6 +++++- Platform/Qemu/SbsaQemu/SbsaQemu.fdf | 1 + 2 files changed, 6 insertions(+), 1 deletion(-) -- 2.45.2 -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#119723): https://edk2.groups.io/g/devel/message/119723 Mute This Topic: https://groups.io/mt/106909458/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
