From: "Chao Li" <lichao@loongson.cn>
To: Leif Lindholm <leif.lindholm@oss.qualcomm.com>,
edk2-devel-groups-io <devel@edk2.groups.io>
Cc: Baoqi Zhang <zhangbaoqi@loongson.cn>,
Dongyan Qian <qiandongyan@loongson.cn>,
Xiangdong Meng <mengxiangdong@loongson.cn>,
maobibo@loongson.cn, lixianglai@loongson.cn
Subject: Re: [edk2-devel] Relationship between loongson virtual platforms?
Date: Tue, 6 May 2025 10:02:43 +0800 [thread overview]
Message-ID: <ba98b130-55a6-4a63-821d-d58458a73515@loongson.cn> (raw)
In-Reply-To: <CAD=n3R0tXU7UO2BN0iu1tchoAfJCmY6h6n9edVV9bBNnL6DCPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hi Leif,
Thanks for the reminder, we will discuss the direction of the
edk2-platforms version where to go in the next few days. :)
Thanks,
Chao
On 2025/4/29 21:02, Leif Lindholm wrote:
> Hi Loongson maintainers across edk2 and edk2-platforms.
>
> I'm going through edk2-platforms to see which platforms are going to
> be impacted by
> https://github.com/tianocore/edk2/pull/10968.
>
> I noticed edk2-platforms LoongArchQemuPkg stopped receiving functional
> updates around the time edk2 OvmfPkg/LoongArchVirt was introduced. Is
> the edk2-platforms version still relevant?
> It appears to have been broken since at least November 2024 because of
> edk2 commit fc9f06de6f7d ("NetworkPkg: mark fixed network PCDs").
>
> /
> Leif
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121306): https://edk2.groups.io/g/devel/message/121306
Mute This Topic: https://groups.io/mt/112519457/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 2355 bytes --]
prev parent reply other threads:[~2025-05-06 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:02 [edk2-devel] Relationship between loongson virtual platforms? Leif Lindholm via groups.io
2025-05-06 2:02 ` Chao Li [this message]
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=ba98b130-55a6-4a63-821d-d58458a73515@loongson.cn \
--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