From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.byosoft.com.cn (mail.byosoft.com.cn [58.240.74.242]) by mx.groups.io with SMTP id smtpd.web09.16812.1630890413858694496 for ; Sun, 05 Sep 2021 18:06:55 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: byosoft.com.cn, ip: 58.240.74.242, mailfrom: gaoliming@byosoft.com.cn) Received: from DESKTOPS6D0PVI ([58.246.60.130]) (envelope-sender ) by 192.168.6.13 with ESMTP for ; Mon, 06 Sep 2021 09:06:29 +0800 X-WM-Sender: gaoliming@byosoft.com.cn X-Originating-IP: 58.246.60.130 X-WM-AuthFlag: YES X-WM-AuthUser: gaoliming@byosoft.com.cn From: "gaoliming" To: , Cc: "'Ard Biesheuvel'" , "'Michael D Kinney'" , "'Leif Lindholm'" , , "'Schaefer, Daniel'" , "'Sunil V L'" , , "'Ard Biesheuvel'" , "'Gerd Hoffmann'" References: In-Reply-To: Subject: =?UTF-8?B?5Zue5aSNOiBbZWRrMi1kZXZlbF0gW1JGQ10gUklTQy1WIFFFTVUgdmlydHVhbCBwYWNrYWdl?= Date: Mon, 6 Sep 2021 09:06:30 +0800 Message-ID: <005f01d7a2bb$6d8e5ef0$48ab1cd0$@byosoft.com.cn> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQKP1mBGcT4NiLtw5RNh9FN+7aIwu6olyN7Q Content-Type: multipart/alternative; boundary="----=_NextPart_000_0060_01D7A2FE.7BB28950" Content-Language: zh-cn ------=_NextPart_000_0060_01D7A2FE.7BB28950 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable 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.=20 =20 I also include OVMF package maintainers for this discussion.=20 =20 Thanks Liming =B7=A2=BC=FE=C8=CB: devel@edk2.groups.io =B4=FA=B1= =ED Abner Chang =B7=A2=CB=CD=CA=B1=BC=E4: 2021=C4=EA9=D4=C25=C8=D5 11:15 =CA=D5=BC=FE=C8=CB: devel@edk2.groups.io =B3=AD=CB=CD: Ard Biesheuvel ; Michael D Kinney ; Leif Lindholm ; ray.ni@intel.com; Liming Gao ; Schaefer, Daniel ; Sunil V L =D6=F7=CC=E2: [edk2-devel] [RFC] RISC-V QEMU virtual package =20 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. =20 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=A1=AFt think this way is necessar= y though). Or can we move those to just under OvmfPkg because OvmfPkg also provides some common drivers for the processor architectures. Thoughts? =20 Thanks Abner ------=_NextPart_000_0060_01D7A2FE.7BB28950 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Abner:

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

 

 I also include OVMF pa= ckage maintainers for this discussion.

<= o:p> 

Thanks

Liming

=B7=A2=BC=FE=C8=CB: devel@edk= 2.groups.io <devel@edk2.groups.io> =B4=FA=B1=ED Abner Chang
= =B7=A2=CB=CD=CA=B1=BC=E4: 2021=C4=EA9=D4=C25=C8=D5 11:15
=CA=D5=BC=FE=C8=CB: devel@edk2.groups.io
= =B3=AD=CB=CD: Ard Biesheuv= el <ard.biesheuvel@arm.com>; Michael D Kinney <michael.d.kinney@in= tel.com>; Leif Lindholm <leif@nuviainc.com>; ray.ni@intel.com; Lim= ing Gao <gaoliming@byosoft.com.cn>; Schaefer, Daniel <daniel.schae= fer@hpe.com>; Sunil V L <sunilvl@ventanamicro.com>
= =D6=F7=CC=E2: [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 cre= ate a folder RiscvVirtPkg under edk2 repo and integrated in the Platform CI= build.

&= nbsp;

Second, RISC-= V edk2 OVMF package leverages some edk2 libraries and drivers from ArmVirtP= kg, 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= =A1=AFt think this way is necessary though). Or can we move those to just u= nder OvmfPkg because OvmfPkg also provides some common drivers for the proc= essor architectures.

Thoughts?

 

Th= anks

Abner

------=_NextPart_000_0060_01D7A2FE.7BB28950--