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

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

> -----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
> >
> >
> > 
> >