Re: [edk2-devel] [RFC] RISC-V QEMU virtual package

["Abner Chang" <abner.chang@hpe.com>]

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.chang@hpe.com>; Ni, Ray <ray.ni@intel.com>; leif@nuviainc.com
> Cc: kraxel@redhat.com; Yao, Jiewen <jiewen.yao@intel.com>; gaoliming
> <gaoliming@byosoft.com.cn>; 'Ard Biesheuvel' <ard.biesheuvel@arm.com>;
> Kinney, Michael D <michael.d.kinney@intel.com>; Schaefer, Daniel
> <daniel.schaefer@hpe.com>; 'Sunil V L' <sunilvl@ventanamicro.com>; 'Ard
> Biesheuvel' <ardb+tianocore@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.ni@intel.com>; devel@edk2.groups.io; leif@nuviainc.com
> > Cc: kraxel@redhat.com; Yao, Jiewen <jiewen.yao@intel.com>; gaoliming
> > <gaoliming@byosoft.com.cn>; 'Ard Biesheuvel'
> <ard.biesheuvel@arm.com>;
> > Kinney, Michael D <michael.d.kinney@intel.com>; Schaefer, Daniel
> > <daniel.schaefer@hpe.com>; 'Sunil V L' <sunilvl@ventanamicro.com>; 'Ard
> > Biesheuvel' <ardb+tianocore@kernel.org>
> > Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package
> >
> >
> >
> > > -----Original Message-----
> > > From: Ni, Ray [mailto:ray.ni@intel.com]
> > > Sent: Friday, September 10, 2021 6:07 PM
> > > To: devel@edk2.groups.io; leif@nuviainc.com; Chang, Abner (HPS
> SW/FW
> > > Technologist) <abner.chang@hpe.com>
> > > Cc: kraxel@redhat.com; Yao, Jiewen <jiewen.yao@intel.com>; gaoliming
> > > <gaoliming@byosoft.com.cn>; 'Ard Biesheuvel'
> > <ard.biesheuvel@arm.com>;
> > > Kinney, Michael D <michael.d.kinney@intel.com>; Schaefer, Daniel
> > > <daniel.schaefer@hpe.com>; 'Sunil V L' <sunilvl@ventanamicro.com>;
> 'Ard
> > > Biesheuvel' <ardb+tianocore@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.chang@hpe.com>
> > > > Cc: devel@edk2.groups.io; kraxel@redhat.com; Yao, Jiewen
> > > <jiewen.yao@intel.com>; gaoliming <gaoliming@byosoft.com.cn>;
> > > > 'Ard Biesheuvel' <ard.biesheuvel@arm.com>; Kinney, Michael D
> > > <michael.d.kinney@intel.com>; Ni, Ray <ray.ni@intel.com>;
> > > > Schaefer, Daniel <daniel.schaefer@hpe.com>; 'Sunil V L'
> > > <sunilvl@ventanamicro.com>; 'Ard Biesheuvel'
> > > > <ardb+tianocore@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
> > > >
> > > >
> > > >
> > > >
> >
> >
> >
> >
> >
> 
> 
> 
> 
>