From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Julien Grall <julien.grall@linaro.org>
Subject: Re: [PATCH RFT] ArmVirtPkg/ArmVirtXen: move from Intel to generic BDS
Date: Mon, 4 Dec 2017 16:15:13 +0000 [thread overview]
Message-ID: <CAKv+Gu_62EVfAiZeQTdxnn-6WrmW5wg7c4ozPRv95GwTx7xudw@mail.gmail.com> (raw)
In-Reply-To: <5a2cd371-35e3-2b1d-39d5-129ef71158b4@redhat.com>
On 1 December 2017 at 10:08, Laszlo Ersek <lersek@redhat.com> wrote:
> On 11/30/17 21:31, Ard Biesheuvel wrote:
>> ArmVirtXen is the only remaining consumer of ArmPlatformPkg's
>> PlatformIntelBdsLib implementation, which is tightly coupled to the
>> deprecated Intel BDS. So move ArmVirtXen to the generic BDS as well,
>> allowing us to get rid of PlatformIntelBdsLib entirely.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> ---
>> ArmVirtPkg/ArmVirtXen.dsc | 14 +++++++++++---
>> ArmVirtPkg/ArmVirtXen.fdf | 3 ++-
>> 2 files changed, 13 insertions(+), 4 deletions(-)
>>
>> diff --git a/ArmVirtPkg/ArmVirtXen.dsc b/ArmVirtPkg/ArmVirtXen.dsc
>> index 11e073287a84..ae43d5990110 100644
>> --- a/ArmVirtPkg/ArmVirtXen.dsc
>> +++ b/ArmVirtPkg/ArmVirtXen.dsc
>> @@ -48,8 +48,9 @@ [LibraryClasses]
>> TimerLib|ArmPkg/Library/ArmArchTimerLib/ArmArchTimerLib.inf
>>
>> CapsuleLib|MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.inf
>> - GenericBdsLib|IntelFrameworkModulePkg/Library/GenericBdsLib/GenericBdsLib.inf
>> - PlatformBdsLib|ArmPlatformPkg/Library/PlatformIntelBdsLib/PlatformIntelBdsLib.inf
>> + UefiBootManagerLib|MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib.inf
>> + BootLogoLib|MdeModulePkg/Library/BootLogoLib/BootLogoLib.inf
>> + PlatformBootManagerLib|ArmPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf
>> CustomizedDisplayLib|MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib.inf
>>
>> [LibraryClasses.common.UEFI_DRIVER]
>> @@ -86,6 +87,7 @@ [PcdsFixedAtBuild.common]
>> gArmTokenSpaceGuid.PcdArmArchTimerFreqInHz|0
>>
>> gEfiMdeModulePkgTokenSpaceGuid.PcdResetOnMemoryTypeInformationChange|FALSE
>> + gEfiMdeModulePkgTokenSpaceGuid.PcdBootManagerMenuFile|{ 0x21, 0xaa, 0x2c, 0x46, 0x14, 0x76, 0x03, 0x45, 0x83, 0x6e, 0x8a, 0xb6, 0xf4, 0x66, 0x23, 0x31 }
>> gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5, 0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0, 0xB4, 0xD1 }
>>
>> [PcdsPatchableInModule.common]
>> @@ -199,7 +201,13 @@ [Components.common]
>> MdeModulePkg/Universal/DevicePathDxe/DevicePathDxe.inf
>> MdeModulePkg/Universal/DisplayEngineDxe/DisplayEngineDxe.inf
>> MdeModulePkg/Universal/SetupBrowserDxe/SetupBrowserDxe.inf
>> - IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe.inf
>> + MdeModulePkg/Universal/BdsDxe/BdsDxe.inf
>> + MdeModulePkg/Application/UiApp/UiApp.inf {
>> + <LibraryClasses>
>> + NULL|MdeModulePkg/Library/DeviceManagerUiLib/DeviceManagerUiLib.inf
>> + NULL|MdeModulePkg/Library/BootManagerUiLib/BootManagerUiLib.inf
>> + NULL|MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenanceManagerUiLib.inf
>> + }
>>
>> OvmfPkg/XenBusDxe/XenBusDxe.inf
>> OvmfPkg/XenPvBlkDxe/XenPvBlkDxe.inf
>> diff --git a/ArmVirtPkg/ArmVirtXen.fdf b/ArmVirtPkg/ArmVirtXen.fdf
>> index 6586ce6be505..50e670254d52 100644
>> --- a/ArmVirtPkg/ArmVirtXen.fdf
>> +++ b/ArmVirtPkg/ArmVirtXen.fdf
>> @@ -177,7 +177,8 @@ [FV.FvMain]
>> INF MdeModulePkg/Universal/DevicePathDxe/DevicePathDxe.inf
>> INF MdeModulePkg/Universal/DisplayEngineDxe/DisplayEngineDxe.inf
>> INF MdeModulePkg/Universal/SetupBrowserDxe/SetupBrowserDxe.inf
>> - INF IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe.inf
>> + INF MdeModulePkg/Universal/BdsDxe/BdsDxe.inf
>> + INF MdeModulePkg/Application/UiApp/UiApp.inf
>>
>> INF OvmfPkg/XenBusDxe/XenBusDxe.inf
>> INF OvmfPkg/XenPvBlkDxe/XenPvBlkDxe.inf
>>
>
> The patch looks fine, and I agree that the main thing that should decide
> about it is testing by Julien.
>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
>
Pushed as 75e2d0e02f1c40a2e4971bd67399028e0b1681c8, after folding in
the changes that Julien tested.
Thanks all.
next prev parent reply other threads:[~2017-12-04 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 20:31 [PATCH RFT] ArmVirtPkg/ArmVirtXen: move from Intel to generic BDS Ard Biesheuvel
2017-12-01 10:08 ` Laszlo Ersek
2017-12-04 16:15 ` Ard Biesheuvel [this message]
2017-12-04 15:19 ` Julien Grall
2017-12-04 15:52 ` Ard Biesheuvel
2017-12-04 15:55 ` Ard Biesheuvel
2017-12-04 16:08 ` Julien Grall
2017-12-04 16:09 ` Ard Biesheuvel
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=CAKv+Gu_62EVfAiZeQTdxnn-6WrmW5wg7c4ozPRv95GwTx7xudw@mail.gmail.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