From: "Rebecca Cran" <rebecca@nuviainc.com>
To: Sami Mujawar <Sami.Mujawar@arm.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
Ard Biesheuvel <Ard.Biesheuvel@arm.com>,
"leif@nuviainc.com" <leif@nuviainc.com>
Cc: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
Jiewen Yao <jiewen.yao@intel.com>,
Rahul Kumar <rahul1.kumar@intel.com>, nd <nd@arm.com>,
Jose Marinho <Jose.Marinho@arm.com>
Subject: Re: [edk2-devel] RFC: Adding support for ARM (RNDR etc.) to RngDxe
Date: Tue, 20 Apr 2021 14:04:19 -0600 [thread overview]
Message-ID: <985081eb-5e3e-fc33-6afa-c9c121412973@nuviainc.com> (raw)
In-Reply-To: <DB7PR08MB309761F021EA3B761AAC241584A60@DB7PR08MB3097.eurprd08.prod.outlook.com>
Hi Sami,
I was wondering if you're still collecting feedback on the design, or if
you have a plan and schedule for the implementation?
--
Rebecca Cran
On 1/15/21 7:51 PM, Sami Mujawar wrote:
> Hi All,
>
> I have shared some initial thoughts on the RNG implementation updates at https://edk2.groups.io/g/devel/files/Designs/2021/0116/EDKII%20-%20Proposed%20update%20to%20RNG%20implementation.pdf
>
> Kindly let me know your feedback or if you have any queries.
>
> Regards,
>
> Sami Mujawar
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran via groups.io
> Sent: 14 January 2021 09:05 PM
> To: Sami Mujawar <Sami.Mujawar@arm.com>; devel@edk2.groups.io; Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>; Ard Biesheuvel <Ard.Biesheuvel@arm.com>; leif@nuviainc.com
> Cc: 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
>
> On 12/10/20 4:26 AM, Sami Mujawar wrote:
>
>> 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 Sami,
>
> I don't see any further discussions on this. Have you made any progress
> with sharing the design documents or scheduling a review?
>
next prev parent reply other threads:[~2021-04-20 20:04 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
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 [this message]
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=985081eb-5e3e-fc33-6afa-c9c121412973@nuviainc.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