public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Abner Chang" <abner.chang@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Leif Lindholm <leif@nuviainc.com>,
	"ray.ni@intel.com" <ray.ni@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	"Schaefer, Daniel" <daniel.schaefer@hpe.com>,
	Sunil V L <sunilvl@ventanamicro.com>
Subject: [RFC] RISC-V QEMU virtual package
Date: Sun, 5 Sep 2021 03:15:22 +0000	[thread overview]
Message-ID: <CS1PR8401MB1144F333CCF7A9C7A56C8BD3FFD19@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2818 bytes --]

             reply	other threads:[~2021-09-05  3:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05  3:15 Abner Chang [this message]
2021-09-06  1:06 ` 回复: [edk2-devel] [RFC] RISC-V QEMU virtual package gaoliming
2021-09-06  4:16   ` Abner Chang
2021-09-06  6:16     ` Yao, Jiewen
2021-09-06 11:08       ` Abner Chang
2021-09-06 11:44         ` Yao, Jiewen
2021-09-06 12:04           ` Ard Biesheuvel
2021-09-06 12:19             ` Gerd Hoffmann
2021-09-06 13:04               ` Abner Chang
2021-09-07  1:09                 ` 回复: " gaoliming
2021-09-07  2:31                   ` Abner Chang
2021-09-07  7:18                 ` Gerd Hoffmann
2021-09-07 17:22         ` Leif Lindholm
2021-09-08 12:31           ` Abner Chang
2021-09-08 13:37             ` Gerd Hoffmann
2021-09-08 15:33               ` Abner Chang
2021-09-08 15:53                 ` Leif Lindholm
2021-09-09  5:23                 ` Gerd Hoffmann
2021-09-10  0:08                   ` Abner Chang
2021-09-10  9:54                     ` Leif Lindholm
2021-09-10 10:06                       ` Ni, Ray
2021-09-11  0:52                         ` Abner Chang
     [not found]                         ` <16A39EA413775DFC.29279@groups.io>
2021-09-18  6:46                           ` Abner Chang
     [not found]                           ` <16A5D7B7D6218B9A.31588@groups.io>
2021-09-18  7:00                             ` Abner Chang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CS1PR8401MB1144F333CCF7A9C7A56C8BD3FFD19@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox