On Wed, 10 Sep 2025 16:13:41 +0100 Debbie Horsfall <[email protected]> wrote:
Hi, > Enable the DM_RNG virtio random number generator driver in order to > consume entropy within U-Boot. This allows U-Boot to inject entropy to the > kernel via UEFI, so the kernel can use that early, for instance for > address layout randomisation, or when the kernel does not provide an > entropy driver itself. The change looks alright, but is a bit useless on its own, since there wouldn't be a usable entropy source by default: - The FVP optionally provides a VIRTIO_RNG device, and this can be simply enabled on the FVP command line (*.virtio_rng.enabled=1). But the normal DTs omit the required DT node, since that would cause SErrors when the command line option is not provided, so this still doesn't show up, even when now CONFIG_VIRTIO_RNG is set. - The FVP model can provide the ARMv8.4 FEAT_RNG system registers (cluster<x>.has_rndr=1), but the feature is not enabled in any of the VExpress64 builds. This feature uses auto-detection, so it doesn't hurt to have it always in. So I would suggest to enable CONFIG_RNG_ARM_RNDR here as well (another imply line?), to make this more useful. Cheers, Andre > > Signed-off-by: Debbie Horsfall <[email protected]> > --- > board/armltd/vexpress64/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/board/armltd/vexpress64/Kconfig b/board/armltd/vexpress64/Kconfig > index 7e8709444fe..f413c51ac43 100644 > --- a/board/armltd/vexpress64/Kconfig > +++ b/board/armltd/vexpress64/Kconfig > @@ -21,6 +21,7 @@ config VEXPRESS64_BASE_MODEL > imply EFI_SET_TIME if DM_RTC > select LINUX_KERNEL_IMAGE_HEADER > select POSITION_INDEPENDENT > + imply DM_RNG > > choice > prompt "VExpress64 board variant"
