diff options
author | Patrick Williams <patrick@stwcx.xyz> | 2020-03-02 21:20:12 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-09-15 05:01:46 +0300 |
commit | 1976e316071353ccc515d4a53e49c35c9f77e218 (patch) | |
tree | 57179e3c3d03e3f7521a38b2bbb80bdbf3069af8 /.github | |
parent | 3fd3e124be802eafc7b1a14f948dc9d2edc6d588 (diff) | |
download | openbmc-1976e316071353ccc515d4a53e49c35c9f77e218.tar.xz |
rng-tools: use 'hw-rng' to disable libjitterentropy
The warrior version of rng-tools introduced an optional PACKAGECONFIG,
which was enabled by default, called `libjitterentropy`. For BMC chips
which have a hardware RNG, this is not a necessary feature, and causes
a noticeable delay in the start of the rngd. On systems with very low
IO activity we are seeing cases of what appears to be hangs.
Define a machine feature which can be used to disable the PACKAGECONFIG
for machines which contain a BMC chip with a hardware RNG. Aspeed has
one which is supported; Nuvoton currently does not.
(From meta-phosphor rev: e60e3098c981ece700a855ddc0daf2bdddf0a7da)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie4a26e6ca22fe0d7ee9470062f5b26ac733454f2
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions