public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: Sami Mujawar <Sami.Mujawar@arm.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
	Ard Biesheuvel <Ard.Biesheuvel@arm.com>,
	"rebecca@nuviainc.com" <rebecca@nuviainc.com>,
	"rfc@edk2.groups.io" <rfc@edk2.groups.io>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Rahul Kumar <rahul1.kumar@intel.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] RFC: Adding support for ARM (RNDR etc.) to RngDxe
Date: Thu, 10 Dec 2020 12:52:13 +0000	[thread overview]
Message-ID: <20201210125213.GQ1664@vanye> (raw)
In-Reply-To: <DB7PR08MB3097B69CE3A326D08B3403EC84CB0@DB7PR08MB3097.eurprd08.prod.outlook.com>

Hi Sami,

JPGs work, but preferably published in a location where they're
unlikely to be deleted, and posted as URLs.

https://app.diagrams.net/ doesn't require a licensed application to
edit, and can be "saved to github" for example.

Please make sure to use the diagrams to support/clarify the mailing
list conversation rather than replacing it.

Best Regards,

Leif

On Thu, Dec 10, 2020 at 11:26:26 +0000, Sami Mujawar wrote:
> Hi All,
> 
> I am working on the TRNG FW API interface and will share more details for the discussion soon.
> We had some thoughts about streamlining the RngDxe implementations
> and would like to share some diagrams for the discussion.
> My diagrams are in Visio that I can export as JPG images. However, I
> am open to switching to any other suggested tool.
> 
> Hi Leif,
> 
> Can you suggest on how we can collaborate to share diagrams/documents, please?
> 
> Regards,
> 
> Sami Mujawar
> 
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Samer El-Haj-Mahmoud via groups.io
> Sent: 09 December 2020 04:48 AM
> To: devel@edk2.groups.io
> Cc: rfc@edk2.groups.io; Jiewen Yao <jiewen.yao@intel.com>; Rahul Kumar <rahul1.kumar@intel.com>
> Subject: Re: [edk2-devel] RFC: Adding support for ARM (RNDR etc.) to RngDxe
> 
> There is also the TRNG FW API, which is an architected SMC firmware interface:
> 
> https://developer.arm.com/documentation/den0098/latest/
> 
> ________________________________
> From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> on behalf of Rebecca Cran via groups.io <rebecca=nuviainc.com@groups.io<mailto:rebecca=nuviainc.com@groups.io>>
> Sent: Tuesday, December 8, 2020, 11:33 PM
> To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
> Cc: rfc@edk2.groups.io<mailto:rfc@edk2.groups.io>; Jiewen Yao; Rahul Kumar
> Subject: [edk2-devel] RFC: Adding support for ARM (RNDR etc.) to RngDxe
> 
> Currently, RngDxe in SecurityPkg only supports Intel, with RdRand support.
> 
> 
> This RFC is to start a discussion about adding support for ARM.
> 
> 
> I have a Git branch with support for the optional ARMv8.5 RNDR
> instruction at https://github.com/bcran/edk2/commits/bcran-rndr which
> moves the existing Intel support into a Rand directory, and adds code to
> support RNDR in a new AArch64 directory.
> 
> There are other RNG implementations available for ARM, including
> platform-specific approaches on Graviton
> (https://lwn.net/Articles/790304/) and other platforms, so a more
> thorough rearchitecting/redesign may be desired.
> 
> 
> --
> Rebecca Cran
> 
> 
> 
> 
> 
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> 

  reply	other threads:[~2020-12-10 12:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  4:32 RFC: Adding support for ARM (RNDR etc.) to RngDxe Rebecca Cran
2020-12-09  4:47 ` [edk2-devel] " Samer El-Haj-Mahmoud
2020-12-10 11:26   ` Sami Mujawar
2020-12-10 12:52     ` Leif Lindholm [this message]
2020-12-10 13:43       ` [edk2-rfc] " Yao, Jiewen
2021-01-14 21:05     ` Rebecca Cran
2021-01-16  2:51       ` Sami Mujawar
2021-02-10 22:49         ` Rebecca Cran
2021-02-11 18:26           ` Ard Biesheuvel
2021-04-20 20:04         ` Rebecca Cran
2021-04-22  9:30           ` Sami Mujawar
2021-04-26 14:45             ` Rebecca Cran
2021-04-26 21:28             ` Rebecca Cran
2021-04-26 21:45               ` [EXTERNAL] " Bret Barkelew
2021-04-27 13:22                 ` Sami Mujawar

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=20201210125213.GQ1664@vanye \
    --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