public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, leif@nuviainc.com, andrew.goodbody@linaro.org
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Thomas Abraham <thomas.abraham@arm.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] Cannot build due to recent change
Date: Fri, 2 Oct 2020 11:18:20 +0200	[thread overview]
Message-ID: <baaa442c-eea6-7a0a-049c-c034e682105f@redhat.com> (raw)
In-Reply-To: <20201001104332.GG5623@vanye>

on a tangent:

On 10/01/20 12:43, Leif Lindholm wrote:

> if the platform port produces EFI_RNG_PROTOCOL
> from some onboard hw, you can use the approach from edk2-platforms
> commit 1e09147a01ae ("Platforms/RaspberryPi: Fix RPi4 RngLib build error").

Emphasis on "onboard hw".

I find it incredibly attractive and good system design that

  Silicon/Broadcom/Bcm283x/Drivers/Bcm2838RngDxe

can *exist*, because the underlying *platform hardware* also exists. I
wish we had something similar for virt, i.e. randomness available from
just a handful of fixed location MMIO registers. Randomness is needed
way earlier than when various bus enumerations occur, such as PCI, or
even virtio-mmio.

See also: why virtio-serial is unusable as a real debug output device.

Yes, I know, on Intel there's RDRAND and friends; they didn't have good
press, and it's still unclear to me how much one can count on RDRAND's
presence on the various QEMU/KVM CPU models.

/end tangent

Laszlo


      parent reply	other threads:[~2020-10-02  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 12:16 Cannot build due to recent change andrew.goodbody
2020-10-01 10:43 ` [edk2-devel] " Leif Lindholm
2020-10-01 11:06   ` Andrew Goodbody
2020-10-01 11:12     ` Leif Lindholm
2020-10-01 11:07   ` Sami Mujawar
2020-10-02  9:18   ` Laszlo Ersek [this message]

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-list 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=baaa442c-eea6-7a0a-049c-c034e682105f@redhat.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox