One corection. > -----Original Message----- > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of > Abner Chang > Sent: Saturday, September 18, 2021 2:46 PM > To: devel@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist) > <abner.ch...@hpe.com>; Ni, Ray <ray...@intel.com>; l...@nuviainc.com > Cc: kra...@redhat.com; Yao, Jiewen <jiewen....@intel.com>; gaoliming > <gaolim...@byosoft.com.cn>; 'Ard Biesheuvel' <ard.biesheu...@arm.com>; > Kinney, Michael D <michael.d.kin...@intel.com>; Schaefer, Daniel > <daniel.schae...@hpe.com>; 'Sunil V L' <suni...@ventanamicro.com>; 'Ard > Biesheuvel' <ardb+tianoc...@kernel.org> > Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package > > Hi all, below is the plan to move some module/libraries from Arm*Pkg to > other packages for RiscVVirtPkg and RiscVPkg. > > 1. FdtClientDxe - which is a useful protocol for parsing FDT nodes. Move to > stay with FdtLib under EmbeddedPkg. gFdtClientProtocolGuid will be also > moved to under EmbeddedPkg. > 2. HighMemDxe - Move to under OvmfPkg/Fdt > 3. FdtPciHostBridgeLib and FdtPciPcdProducerLib - Move to under > OvmfPkg/Fdt > The PCD PcdPciIoTranslation is used by above two libraries and > ArmPciCpuIo2Dxe, RiscVVirtPkg will use that PCD as well. RiscVPkg may > provide its own CPU_IO2 protocol and use this PCD as ARM does. > The definition of PcdPciIoTranslation will be moved to under > MdeModulePkg for ARM and RISC-V. PcdPciIoTranslation will be moved to under MdePkg/
Abner > 4. VirtioFdtDxe - Will be moved to under OvmfPkg/Fdt > Let me know if you have any opinions. > > Regards, > Abner > > > -----Original Message----- > > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of > > Abner Chang > > Sent: Saturday, September 11, 2021 8:52 AM > > To: Ni, Ray <ray...@intel.com>; devel@edk2.groups.io; l...@nuviainc.com > > Cc: kra...@redhat.com; Yao, Jiewen <jiewen....@intel.com>; gaoliming > > <gaolim...@byosoft.com.cn>; 'Ard Biesheuvel' > <ard.biesheu...@arm.com>; > > Kinney, Michael D <michael.d.kin...@intel.com>; Schaefer, Daniel > > <daniel.schae...@hpe.com>; 'Sunil V L' <suni...@ventanamicro.com>; 'Ard > > Biesheuvel' <ardb+tianoc...@kernel.org> > > Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package > > > > > > > > > -----Original Message----- > > > From: Ni, Ray [mailto:ray...@intel.com] > > > Sent: Friday, September 10, 2021 6:07 PM > > > To: devel@edk2.groups.io; l...@nuviainc.com; Chang, Abner (HPS > SW/FW > > > Technologist) <abner.ch...@hpe.com> > > > Cc: kra...@redhat.com; Yao, Jiewen <jiewen....@intel.com>; gaoliming > > > <gaolim...@byosoft.com.cn>; 'Ard Biesheuvel' > > <ard.biesheu...@arm.com>; > > > Kinney, Michael D <michael.d.kin...@intel.com>; Schaefer, Daniel > > > <daniel.schae...@hpe.com>; 'Sunil V L' <suni...@ventanamicro.com>; > 'Ard > > > Biesheuvel' <ardb+tianoc...@kernel.org> > > > Subject: RE: [edk2-devel] [RFC] RISC-V QEMU virtual package > > > > > > I asked similar question to Mike who initially set up the CI. > > > The answer was: it's ok to pull a edk2-platform code in CI process to > > > verify > > > edk2 code change. > > Move RiscVPkg/RiscVPlatformPkg to under edk2 rather than have it under > > edk2-platforms makes more sense to me, and just leave RISC-V platform > > code under edk2-platforms. > > (Or we can merge RiscVPlatformPkg into RiscVPkg and put RiscVPkg under > > edk2 because it seems not necessary to have the common platform code in > > the separate package.) > > This is not only the matter of RISC-V packages location, CI for any RISC-V > > change is also required. > > > > Abner > > > > > > > > > -----Original Message----- > > > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of > Leif > > > Lindholm > > > > Sent: Friday, September 10, 2021 5:55 PM > > > > To: Chang, Abner <abner.ch...@hpe.com> > > > > Cc: devel@edk2.groups.io; kra...@redhat.com; Yao, Jiewen > > > <jiewen....@intel.com>; gaoliming <gaolim...@byosoft.com.cn>; > > > > 'Ard Biesheuvel' <ard.biesheu...@arm.com>; Kinney, Michael D > > > <michael.d.kin...@intel.com>; Ni, Ray <ray...@intel.com>; > > > > Schaefer, Daniel <daniel.schae...@hpe.com>; 'Sunil V L' > > > <suni...@ventanamicro.com>; 'Ard Biesheuvel' > > > > <ardb+tianoc...@kernel.org> > > > > Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package > > > > > > > > On Fri, Sep 10, 2021 at 00:08:12 +0000, Chang, Abner (HPS SW/FW > > > Technologist) wrote: > > > > > > Move it to > > > OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgLibMMIO.{c,inf} ? > > > > > The naming sounds good to me. > > > > > > > > > > Another question, > > > > > Can CI build the package with dependency of edk2-platform? > Currently > > > > > RiscVPkg in under edk2-platform and the modules provided by > > RiscVPkg > > > > > are referred by RiscVVirPkg. > > > > > > > > Ideally not. > > > > > > > > I think this serves as a reminder that RISC-V/ProcessorPkg should move > > > > over to edk2. > > > > > > > > / > > > > Leif > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#80850): https://edk2.groups.io/g/devel/message/80850 Mute This Topic: https://groups.io/mt/85405739/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
