public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, "Ni, Ray" <ray.ni@intel.com>,
	"Dong, Guo" <guo.dong@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Ma, Maurice" <maurice.ma@intel.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] UefiPayloadPkg: Enhance UEFI payload for coreboot and Slim Bootloader
Date: Tue, 2 Apr 2019 01:53:51 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8BB330@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <8d11ec47-73ee-484e-460e-1679079b1385@redhat.com>

> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Monday, April 01, 2019 10:05 PM
> To: Ni, Ray; Dong, Guo; edk2-devel@lists.01.org
> Cc: Wu, Hao A; Kinney, Michael D; Ma, Maurice; David Woodhouse
> Subject: Re: [edk2] [PATCH] UefiPayloadPkg: Enhance UEFI payload for
> coreboot and Slim Bootloader
> 
> (+David)
> 
> On 03/29/19 06:15, Ni, Ray wrote:
> >
> > Guo,
> > Just to double confirm: UefiPayloadPkg will not require Legacy8254 timer
> support.
> > The old packages Coreboot*Pkgs will be removed.
> > Which means now only QEMU/OVMF needs the Legacy8254 support.
> >
> > Laszlo,
> > Now since QEMU/OVMF is the only consumer of the Legacy8254 driver, do
> you
> > agree that the Legacy8254 is moved to OvmfPkg?
> > Note: We agreed that Legacy8259 will be moved to OvmfPkg/Csm directory
> and
> > that decision is not going to be changed by this new situation.
> 
> The last status (up to & including comment 12) in
> <https://bugzilla.tianocore.org/show_bug.cgi?id=1496> was that:
> 
> (1) 8254TimerDxe would remain a generic driver, with the minimal
> interrupt controller programming that it needs flattened into it (no
> dependency on gEfiLegacy8259ProtocolGuid)
> 
> (2) the 8259InterruptControllerDxe driver (producing
> gEfiLegacy8259ProtocolGuid) would move under OvmfPkg/Csm.
> 
> Now, if 8254TimerDxe becomes specific to OvmfPkg, then I think it's not
> necessary to modify it -- it can continue depending on
> gEfiLegacy8259ProtocolGuid. Simply move both drivers from PcAtChipsetPkg
> to OvmfPkg. (Note: *not* to OvmfPkg/Csm).
> 
> Hao: can you please update
> <https://bugzilla.tianocore.org/show_bug.cgi?id=1496> accordingly? (If
> you agree, that is.)

Sure.
I will double confirm the latest direction and update the above BZ.

Best Regards,
Hao Wu

> 
> Thanks
> Laszlo

  reply	other threads:[~2019-04-02  1:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  0:33 [PATCH] UefiPayloadPkg: Enhance UEFI payload for coreboot and Slim Bootloader Guo Dong
2019-03-29  5:15 ` Ni, Ray
2019-03-29 15:07   ` Dong, Guo
2019-04-01 14:05   ` Laszlo Ersek
2019-04-02  1:53     ` Wu, Hao A [this message]
2019-04-03 14:13 ` Ma, Maurice
     [not found]   ` <734D49CCEBEEF84792F5B80ED585239D5C0E0C06@SHSMSX104.ccr.corp.intel.com>
2019-04-11 15:38     ` Ma, Maurice
2019-04-11 15:58       ` Guo Dong
  -- strict thread matches above, loose matches on Subject: below --
2019-04-11 15:03 Guo Dong

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=B80AF82E9BFB8E4FBD8C89DA810C6A093C8BB330@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