public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
	"sudeep.holla@arm.com" <sudeep.holla@arm.com>
Subject: Re: [PATCH edk2-platforms] Platform/ARM: remove ReportStatusCodeLib resolutions
Date: Tue, 17 Oct 2017 15:05:49 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E16CE3B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu_fPSeahaRis8+KBEA9VD=ViuFXd3t8cGU4y5rNE0xQhw@mail.gmail.com>

Ard:
  MdeModulePkg\Universal\Acpi\FirmwarePerformanceDataTableDxe depends on some status code to fill basic boot FPDT record in FPDT table. Those status codes are reported from DxeCore. For FPDT table, DxeCore must link the real report status code. It links DXE version library instance. 

Thanks
Liming
> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> Sent: Tuesday, October 17, 2017 4:44 PM
> To: Gao, Liming <liming.gao@intel.com>
> Cc: edk2-devel@lists.01.org; leif.lindholm@linaro.org; sudeep.holla@arm.com
> Subject: Re: [edk2] [PATCH edk2-platforms] Platform/ARM: remove ReportStatusCodeLib resolutions
> 
> On 17 October 2017 at 01:53, Gao, Liming <liming.gao@intel.com> wrote:
> > Ard:
> >   MdeModulePkg\Library\RuntimeDxeReportStatusCodeLib\RuntimeDxeReportStatusCodeLib.inf is designed for Runtime driver. If
> you require StatusCode at runtime, you can use this library instance.
> >
> 
> Thanks Liming.
> 
> I wrongly assumed that these platforms have no use for status code,
> but apparently, it is required for the FPDT table?

  reply	other threads:[~2017-10-17 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 18:03 [PATCH edk2-platforms] Platform/ARM: remove ReportStatusCodeLib resolutions Ard Biesheuvel
2017-10-17  0:53 ` Gao, Liming
2017-10-17  8:41   ` Alexei Fedorov
2017-10-17  8:42     ` Ard Biesheuvel
2017-10-17  8:43   ` Ard Biesheuvel
2017-10-17 15:05     ` Gao, Liming [this message]
2017-10-17 15:21       ` Ard Biesheuvel
2017-10-17 10:24 ` Sudeep Holla

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E16CE3B@SHSMSX104.ccr.corp.intel.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