On 3/1/24 12:45, Leif Lindholm wrote:
Thank you.
OK, that's logically consistent.
So we'd need an ArmLibNull in MdePkg until ArmLib itself migrates there
(ideally subsumed into BaseLib).
From what Jiewen said, it doesn't seem that creating an ArmLibNull
in the MdePkg is necessary (unless I
Right, if it is only required by ARM, then it should under ARM section.
Thank you
Yao, Jiewen
> -Original Message-
> From: Leif Lindholm
> Sent: Friday, March 1, 2024 7:45 PM
> To: Yao, Jiewen ; Pierre Gondois
> ; devel@edk2.groups.io
> Cc: Ard Biesheuvel ; Liming Gao
> ; Kinney, Michael
Thank you.
OK, that's logically consistent.
So we'd need an ArmLibNull in MdePkg until ArmLib itself migrates there
(ideally subsumed into BaseLib).
But the dependency in .inf should still be able to be declared under
[LibraryClasses.AArch64, LibraryClasses.ARM]?
Regards,
Leif
On 2024-03-01
Sure.
When we say "dependency", what we really mean is the dependency in INF file,
not "dependency" in DSC file.
>From package release perspective, only INF is the interface to other package.
The DSC is only the package internal stuff, you can create multiple DSCs or
add/remove DSC freely.
Ha
Hello Leif,
I think the following files:
- ArmPkg/Include/Chipset/AArch64.h
- ArmPkg/Include/Chipset/AArch64Mmu.h
- ArmPkg/Include/Chipset/ArmV7.h
- ArmPkg/Include/Chipset/ArmV7Mmu.h
also need to be moved to the MdePkg. Otherwise the MdePkg
would depend on the ArmPkg, cf. ArmLib.h:
#ifdef MDE_CP
Related to https://bugzilla.tianocore.org/show_bug.cgi?id=4121, but not
resolving it. (Nearly?) all of ArmPkg describes industry standard
behaviour, and hence according to general rules, ought to live in MdePkg.
Addressing this will however be a substantial task.
Take a first step by moving the Ar
