Abner:

 If these modules are shared by ARM and RISC-V, they should not be ARM specific modules. I prefer to move them into OvmfPkg. Now, ArmVirtPkg also includes the modules from OvmfPkg.

 I also include OVMF package maintainers for this discussion.

Thanks

Liming

发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Abner Chang
发送时间: 2021年9月5日 11:15
收件人: devel@edk2.groups.io
抄送: Ard Biesheuvel <ard.biesheuvel@arm.com>; Michael D Kinney <michael.d.kinney@intel.com>; Leif Lindholm <leif@nuviainc.com>; ray.ni@intel.com; Liming Gao <gaoliming@byosoft.com.cn>; Schaefer, Daniel <daniel.schaefer@hpe.com>; Sunil V L <sunilvl@ventanamicro.com>
主题: [edk2-devel] [RFC] RISC-V QEMU virtual package

Hi all,

We currently have RISC-V edk2 OVMF package that can boot to Linux kernel on QEMU RISC-V virt platform.

First at all, we would like to create a folder RiscvVirtPkg under edk2 repo and integrated in the Platform CI build.

Second, RISC-V edk2 OVMF package leverages some edk2 libraries and drivers from ArmVirtPkg, such as FDT related modules for PCI bus, host bridge and etc. We would like to move those generic virtual drivers to

a common folder for ARM and RISC-V (I don’t think this way is necessary though). Or can we move those to just under OvmfPkg because OvmfPkg also provides some common drivers for the processor architectures.

Thoughts?

Thanks

Abner