From: "Leif Lindholm via groups.io" <leif.lindholm=oss.qualcomm.com@groups.io>
To: devel@edk2.groups.io, ajan.zhong@newfw.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: Re: [edk2-devel] Move ArmPkg/Drivers/CpuDxe to UefiCpuPkg/CpuDxeArm
Date: Thu, 13 Mar 2025 08:36:27 +0000 [thread overview]
Message-ID: <CAD=n3R3vLuN_KFj66PBs5VXS=P7XbNuOJ7JqJY184Jxkj6yp9A@mail.gmail.com> (raw)
In-Reply-To: <WbpI.1741610143360667504.czdG@groups.io>
+cc remaining ArmPkg maintainers
On Mon, 10 Mar 2025 at 12:35, Ajan <ajan.zhong@newfw.com> wrote:
>
> Hi all,
>
> As continues work to this discussion thread: https://edk2.groups.io/g/devel/topic/patch_v5_2_6/102725178
>
> I am going to move ArmPkg/Drivers/CpuDxe to UefiCpuPkg/CpuDxeArm with this drafted PR:
> https://github.com/tianocore/edk2/pull/10836
>
> CpuDxe in ArmPkg depends on following items:
> 1. Move header files from ArmPkg/Include/Library to MdePkg/Include/Library:
> ArmMmuLib.h
> DefaultExceptionLib.h
> 2. Move Guids from ArmPkg to MdePkg:
> gArmTokenSpaceGuid
> gArmMpCoreInfoGuid
> 3. Move PCDs from ArmPkg to MdePkg:
> PcdRemapUnusedMemoryNx
> PcdVFPEnabled
>
> All these dependencies are created as separated patch in PR listed above.
>
> Also, once this CpuDxe is moved from ArmPkg/Drivers/CpuDxe to UefiCpuPkg/CpuDxeArm, we need to create PR to update corresponding ArmPkg/Drivers/CpuDxe.inf to UefiCpuPkg/CpuDxeArm.inf in edk2-platform to adapt this change.
>
> Any suggestion or concerns are welcome.
>
> Thanks.
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121195): https://edk2.groups.io/g/devel/message/121195
Mute This Topic: https://groups.io/mt/111617617/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
parent reply other threads:[~2025-03-13 8:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <WbpI.1741610143360667504.czdG@groups.io>]
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='CAD=n3R3vLuN_KFj66PBs5VXS=P7XbNuOJ7JqJY184Jxkj6yp9A@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