From: "Ni, Ray" <ray.ni@intel.com>
To: "Dong, Guo" <guo.dong@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>
Cc: "Wu, Hao A" <hao.a.wu@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Ma, Maurice" <maurice.ma@intel.com>
Subject: Re: [PATCH] UefiPayloadPkg: Enhance UEFI payload for coreboot and Slim Bootloader
Date: Fri, 29 Mar 2019 05:15:02 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C0A2E99@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190329003332.1876-1-guo.dong@intel.com>
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.
Thanks,
Ray
> -----Original Message-----
> From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Guo
> Dong
> Sent: Friday, March 29, 2019 8:34 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH] UefiPayloadPkg: Enhance UEFI payload for coreboot
> and Slim Bootloader
>
> CorebootModulePkg and CorebootPayloadPkg originally supports coreboot
> only.
> In order to support other bootloaders, such as Slim Bootloader, they need
> be updated to be more generic.
> UEFI Payload (UefiPayloadPkg) a converged package from
> CorebootModulePkg
> and CorebootPayloadPkg with following updates:
> a. Support both coreboot and Slim Bootloader
> b. Removed SataControllerDxe and BaseSerialPortLib16550 to use EDK2
> modules
> c. Support passing bootloader parameter to UEFI payload, e.g. coreboot
> table from coreboot or HOB list from Slim Bootloader
> d. Using GraphicsOutputDxe from EDK2 with minor change instead of FbGop
> e. Remove the dependency to IntelFrameworkPkg and
> IntelFrameworkModulePkg
> and QuarkSocPkg
> f. Use BaseDebugLibSerialPort library as DebugLib
> g. Use HPET timer, drop legacy 8254 timer support
> h. Use BaseXApicX2ApicLib instead of BaseXApicLib
> i. Other clean ups
>
> On how UefiPayloadPkg could work with coreboot/Slim Bootloader, please
> refer UefiPayloadPkg/BuildAndIntegrationInstructions.txt
>
> Once UefiPayloadPkg is checked-in, CorebootModulePkg and
> CorebootPayloadPkg
> could be retired.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Guo Dong <guo.dong@intel.com>
next prev parent reply other threads:[~2019-03-29 5:15 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 [this message]
2019-03-29 15:07 ` Dong, Guo
2019-04-01 14:05 ` Laszlo Ersek
2019-04-02 1:53 ` Wu, Hao A
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=734D49CCEBEEF84792F5B80ED585239D5C0A2E99@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