On 8 February 2016 at 14:52, Ryan Harkin ryan.harkin@linaro.org wrote:
On 8 February 2016 at 12:55, Ard Biesheuvel ard.biesheuvel@linaro.org wrote:
This adds RngDxe to the Juno build, based on the PseudoRngLib that is based on the generic timer and the cycle counter. This is only intended for development purposes, since PseudoRngLib is UNSAFE FOR PRODUCTION.
Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel ard.biesheuvel@linaro.org
Platforms/ARM/Juno/ArmJuno.dsc | 8 ++++++++ Platforms/ARM/Juno/ArmJuno.fdf | 5 +++++ 2 files changed, 13 insertions(+)
diff --git a/Platforms/ARM/Juno/ArmJuno.dsc b/Platforms/ARM/Juno/ArmJuno.dsc index 9f1cbc2ba243..2c2e333f3cbe 100644 --- a/Platforms/ARM/Juno/ArmJuno.dsc +++ b/Platforms/ARM/Juno/ArmJuno.dsc @@ -293,6 +293,14 @@ ArmPlatformPkg/ArmJunoPkg/Drivers/ArmJunoDxe/ArmJunoDxe.inf
#
- # Random Number Generator driver
I'm wondering if it's worth putting am "UNSAFE FOR PRODUCTION" comment in the .dsc file? Mind you, the name "Pseudo..." should give it away. But a comment might have a slim change of helping those who use Juno as a template to create their own BSP.
Yeah, good point. The git commit log is perhaps not as useful in this regard.