From: WANG Xuerui <i.qemu@xen0n.name>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Song Gao" <gaosong@loongson.cn>, 杨小娟 <yangxiaojuan@loongson.cn>,
"Bibo Mao" <maobibo@loongson.cn>
Subject: On integrating LoongArch EDK2 firmware into QEMU build process
Date: Thu, 30 Mar 2023 22:06:48 +0800 [thread overview]
Message-ID: <1f1d3d9f-c3df-4f29-df66-886410994cc3@xen0n.name> (raw)
Hi,
Recently there are reportedly increased general interest in trying out
LoongArch on top of QEMU, among both end users and organizations; and
the EDK2 firmware port is fully upstreamed since the stable202211
version, and a build suitable for QEMU is already possible with
Platform/Loongson/LoongArchQemuPkg in edk2-platforms. I think providing
pre-built LoongArch firmware would make it much easier to dabble in
system emulation, helping those users. (They currently have to pull a
blob from yangxiaojuan/qemu-binary, and remember to pair certain version
of QEMU with certain revision of the firmware blob. I'm also one of the
users who can't remember which version to use, but I can always build my
own; imagine the difficulty an end user would face!)
So I tried to add a LoongArch build to the list stored in roms/, but
discovered that edk2-platforms seems not included, because all other
platforms' EDK2 packages are directly under the main edk2 repo.
The question is: is integrating a platform package from edk2-platforms
okay under the current build system, so we can arrange to provide
edk2-platforms also as a submodule and go ahead? Or do we (the LoongArch
firmware community) have to change the code organization to make
necessary parts available in the main edk2 repo?
CC-ing target/loongarch maintainers from Loongson too as you may have
more information.
next reply other threads:[~2023-03-30 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:06 WANG Xuerui [this message]
2023-03-31 0:54 ` On integrating LoongArch EDK2 firmware into QEMU build process maobibo
2023-03-31 12:12 ` Gerd Hoffmann
2023-04-01 2:16 ` gaosong
2023-04-01 5:11 ` maobibo
2023-04-03 8:51 ` maobibo
2023-04-03 10:13 ` [edk2-devel] " Chao Li
2023-04-03 10:29 ` Michael Brown
2023-04-03 11:04 ` Gerd Hoffmann
2023-04-04 2:24 ` Chao Li
2023-04-03 10:58 ` Gerd Hoffmann
2023-09-30 20:16 ` WANG Xuerui
2023-10-08 1:09 ` Chao Li
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-all 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=1f1d3d9f-c3df-4f29-df66-886410994cc3@xen0n.name \
--to=i.qemu@xen0n.name \
--cc=gaosong@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=yangxiaojuan@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).