From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12511] rng-tools has forced dependency on jitterentropy-library ; It slows boot considerably
Date: Tue, 28 Jan 2020 18:31:01 +0000 [thread overview]
Message-ID: <bug-12511-163-FHISvke00W@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12511-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12511
--- Comment #1 from Matt Weber <matthew.weber@rockwellcollins.com> ---
Sorry to hear about the boot delay issue. The reason it was added by default
was I noticed the init script had handled a case of adding entropy when a hwrng
wasn't present. I didn't realize the impact when hwrng was enabled.
I agree, I think something like a new kconfig sub option named "enable source
jitterentropy" under rngd might be best (with a solid help description
outlining when to enable it). There isn't a ideal way to get a linux config
option to trigger a dependency in the buildroot build.
We could tailor the initscript and have it check if there is a hwrng enabled by
checking for dev node existence if that is consistance. However we can't
probably depend on the linux config being present and parse-able.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-01-28 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:37 [Buildroot] [Bug 12511] New: rng-tools has forced dependency on jitterentropy-library ; It slows boot considerably bugzilla at busybox.net
2020-01-28 16:03 ` [Buildroot] [Bug 12511] " bugzilla at busybox.net
2020-01-28 18:31 ` bugzilla at busybox.net [this message]
2020-02-05 18:27 ` bugzilla at busybox.net
2020-02-06 13:36 ` bugzilla at busybox.net
2020-02-11 15:02 ` bugzilla at busybox.net
2020-02-13 17:10 ` bugzilla at busybox.net
2021-09-29 20:16 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12511-163-FHISvke00W@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.