public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Cohen, Eugene" <eugene@hp.com>
To: Marvin H?user <Marvin.Haeuser@outlook.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "star.zeng@intel.com" <star.zeng@intel.com>
Subject: Re: Inquiry regarding early DxeIplPeim loading.
Date: Thu, 19 Jul 2018 15:40:00 +0000	[thread overview]
Message-ID: <AT5PR8401MB0340C886BC49F3775A9B30DAB4520@AT5PR8401MB0340.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <VI1PR0801MB179051467F88C6927328159D80520@VI1PR0801MB1790.eurprd08.prod.outlook.com>

Marvin,

> Though to be honest, I am not sure why these PPIs are exposed by
> DxeIplPeim instead of a dedicated module or maybe even PeiCore itself, if
> it's the de facto standard.

When we were originally facing the issue one of the ideas was in fact to move this to PeiCore.  I don't recall why that path wasn't pursued.

> Also, if the change was done to avoid disabling CAR prematurely, why
> wasn't SEC code adapted?

This was an ARM SoC not X86 so the modules involved were different than what you're seeing.  I'm trying to remember the specifics but it was long enough ago that it escapes me and my time machine is broken.

Eugene


      reply	other threads:[~2018-07-19 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 23:19 Inquiry regarding early DxeIplPeim loading Marvin H?user
2018-07-13  9:24 ` Zeng, Star
2018-07-13 13:25   ` Marvin H?user
2018-07-18  9:11     ` Zeng, Star
2018-07-18 21:36     ` Cohen, Eugene
2018-07-19  0:10       ` Marvin H?user
2018-07-19 15:40         ` Cohen, Eugene [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=AT5PR8401MB0340C886BC49F3775A9B30DAB4520@AT5PR8401MB0340.NAMPRD84.PROD.OUTLOOK.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