From: "Wu, Hao A" <hao.a.wu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [edk2] [RFC PATCH v1 0/8] Duplicate 8259/8254 components in OvmfPkg
Date: Thu, 4 Apr 2019 04:05:08 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8BC10F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <563a0d19-fcc9-3a40-c782-1b04704e3b95@redhat.com>
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Wednesday, April 03, 2019 9:01 PM
> To: Wu, Hao A; edk2-devel@lists.01.org
> Cc: Justen, Jordan L; David Woodhouse
> Subject: Re: [edk2] [RFC PATCH v1 0/8] Duplicate 8259/8254 components in
> OvmfPkg
>
> On 04/03/19 14:13, Laszlo Ersek wrote:
> > On 04/03/19 14:10, Laszlo Ersek wrote:
> >> On 04/03/19 09:00, Hao Wu wrote:
> >>> This series is also available at:
> >>> https://github.com/hwu25/edk2/tree/ovmf_8259_8254_rfcv1
> >>>
> >>>
> >>> As a sub-task to remove the IntelFrameworkPkg (BZ-1604),
> >>>
> >>> 8259InterruptControllerDxe driver (PcAtChipsetPkg)
> >>> Legacy8259 protocol (IntelFrameworkPkg)
> >>> 8254TimerDxe driver (PcAtChipsetPkg)
> >>>
> >>> will be removed in the near future. Meanwhile, OVMF will still require
> >>> those components (due to CSM support & HPET emulation stability
> concern).
> >>>
> >>> Thus, the series will copy the below 8259/8254 components:
> >>>
> >>> A. 8259InterruptControllerDxe driver (PcAtChipsetPkg)
> >>> B. Two 8259 related PCDs (PcAtChipsetPkg)
> >>> C. Legacy8259 protocol (IntelFrameworkPkg)
> >>> D. 8254TimerDxe driver (PcAtChipsetPkg)
> >>>
> >>> in the OvmfPkg to address the above-mentioned issue.
> >>>
> >>>
> >>> Tests done for the proposed series:
> >>>
> >>> A. OvmfPkg build pass for VS2015 & GCC5 tool chains;
> >>> B. Boot to Shell with commands:
> >>> qemu-system-x86_64.exe -pflash <SOME_PATH>\OVMF.fd -debugcon
> file:boot.log -global isa-debugcon.iobase=0x402
> >>> qemu-system-x86_64.exe -machine q35 -pflash
> <SOME_PATH>\OVMF.fd -debugcon file:boot.log -global isa-
> debugcon.iobase=0x402
> >>> C. 'stall X' command under Shell to verify the timer is working properly.
> >>>
> >>>
> >>> (Please note that there will be a subsequent patch to remove the
> 8259/8254
> >>> components after platforms dropping the dependencies on them.)
> >>>
> >>> Cc: Jordan Justen <jordan.l.justen@intel.com>
> >>> Cc: Laszlo Ersek <lersek@redhat.com>
> >>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >>> Cc: David Woodhouse <dwmw2@infradead.org>
> >>> Cc: Ray Ni <ray.ni@intel.com>
> >>>
> >>>
> >>> Hao Wu (8):
> >>> OvmfPkg: Copy 8259InterruptControllerDxe driver from PcAtChipsetPkg
> >>> OvmfPkg: Copy Legacy8259 protocol definitions from
> IntelFrameworkPkg
> >>> OvmfPkg/OvmfPkg.dec: Add 8259-related PCDs in OVMF DEC file
> >>> OvmfPkg/8259InterruptControllerDxe: Update to make it build for
> OVMF
> >>> OvmfPkg/AcpiPlatformDxe: Consume the 8259 PCD defined in OvmfPkg
> >>> OvmfPkg: Copy 8254TimerDxe driver from PcAtChipsetPkg
> >>> OvmfPkg/8254TimerDxe: Update to make it build for OVMF
> >>> OvmfPkg: Update DSC/FDF files to consume 8259/8254 drivers in
> OvmfPkg
> >>
> >> While I'm reviewing the patches individually, let me make some general
> >> comments:
> >>
> >> - please don't push the series before April 9th (i.e., before the end of
> >> the file addition/removal freeze due to
> >> <https://bugzilla.tianocore.org/show_bug.cgi?id=1373>)
> >>
> >> - if/when you push the series, please make sure that *all* files added
> >> (copied) under OvmfPkg get the new license block format, i.e. the SPDX
> >> license identifier only.
Hello Laszlo,
Actually, I plan to send out another version of the series right after the
file add/remove freeze. If no new comments at that time, I will push the
changes then.
> >
> > ... in fact, at that time, the license blocks under the *source*
> > packages (PcAtChipsetPkg and IntelFrameworkPkg) will have been
> updated,
> > so you will have to redo the copying steps anyway (and you can verify
> > those on your end: "git show --find-copies-harder" should show now
> > modifications as part of the copy operations).
>
> Sigh. I meant
>
> "git show --find-copies-harder" should show *no* modifications as part
> of the copy operations
I will ensure this before sending out the new series.
Best Regards,
Hao Wu
>
> Laszlo
prev parent reply other threads:[~2019-04-04 4:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 7:00 [RFC PATCH v1 0/8] Duplicate 8259/8254 components in OvmfPkg Hao Wu
2019-04-03 7:00 ` [RFC PATCH v1 1/8] OvmfPkg: Copy 8259InterruptControllerDxe driver from PcAtChipsetPkg Hao Wu
2019-04-03 12:05 ` Laszlo Ersek
2019-04-03 7:00 ` [RFC PATCH v1 2/8] OvmfPkg: Copy Legacy8259 protocol definitions from IntelFrameworkPkg Hao Wu
[not found] ` <945615d3-5d8f-659a-a8c4-7320f108ab88@redhat.com>
2019-04-04 2:44 ` [edk2] " hao.a.wu
2019-04-03 7:00 ` [RFC PATCH v1 3/8] OvmfPkg/OvmfPkg.dec: Add 8259-related PCDs in OVMF DEC file Hao Wu
2019-04-03 12:39 ` Laszlo Ersek
2019-04-04 2:56 ` [edk2] " Wu, Hao A
2019-04-03 7:00 ` [RFC PATCH v1 4/8] OvmfPkg/8259InterruptControllerDxe: Update to make it build for OVMF Hao Wu
2019-04-03 12:46 ` Laszlo Ersek
2019-04-04 3:02 ` [edk2] " Wu, Hao A
2019-04-03 7:00 ` [RFC PATCH v1 5/8] OvmfPkg/AcpiPlatformDxe: Consume the 8259 PCD defined in OvmfPkg Hao Wu
2019-04-03 12:48 ` Laszlo Ersek
2019-04-03 7:00 ` [RFC PATCH v1 6/8] OvmfPkg: Copy 8254TimerDxe driver from PcAtChipsetPkg Hao Wu
2019-04-03 12:50 ` Laszlo Ersek
2019-04-03 7:00 ` [RFC PATCH v1 7/8] OvmfPkg/8254TimerDxe: Update to make it build for OVMF Hao Wu
2019-04-03 12:52 ` Laszlo Ersek
2019-04-03 7:00 ` [RFC PATCH v1 8/8] OvmfPkg: Update DSC/FDF files to consume 8259/8254 drivers in OvmfPkg Hao Wu
2019-04-03 12:57 ` Laszlo Ersek
2019-04-03 12:10 ` [RFC PATCH v1 0/8] Duplicate 8259/8254 components " Laszlo Ersek
2019-04-03 12:13 ` Laszlo Ersek
[not found] ` <563a0d19-fcc9-3a40-c782-1b04704e3b95@redhat.com>
2019-04-04 4:05 ` Wu, Hao A [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=B80AF82E9BFB8E4FBD8C89DA810C6A093C8BC10F@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