diff options
| author | Tom Rini <trini@konsulko.com> | 2024-01-09 09:00:39 -0500 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2024-01-09 09:00:39 -0500 |
| commit | c7937a41992298752b9b424b9e4d222dfc157915 (patch) | |
| tree | 5d1b7f0c0567ea34219d64b1cd76aea0b6c23d0b /.github | |
| parent | c5e461fbf7cc72f0c1c8a79226b6a5170e56cb4d (diff) | |
| parent | 1351cd3b4b1b18cafa4893a44378ca6b1d091c8e (diff) | |
| download | u-boot-c7937a41992298752b9b424b9e4d222dfc157915.zip u-boot-c7937a41992298752b9b424b9e4d222dfc157915.tar.gz u-boot-c7937a41992298752b9b424b9e4d222dfc157915.tar.bz2 | |
Merge tag 'rng-2024-04-rc1' of https://gitlab.denx.de/u-boot/custodians/u-boot-efi
Pull request rng-2024-04-rc1
QEMU does not provide information in the device-tree if the ARMv8.5 RNDR
or the RISC-V Zkr RNG have been enabled on the command line.
In different parts of our code we assume that the first RNG device is the
one to be used. Therefore it is preferable to detect the availability of
said devices already in the bind method.
There has been a related discussion if the U_BOOT_DRVINFO() macro should be
used for architectural devices
(https://lore.kernel.org/u-boot/20231031125552.26698-1-heinrich.schuchardt@canonical.com/).
This aspect is not touched by this series.
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions