From: "Chao Li" <lichao@loongson.cn>
To: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Leif Lindholm <quic_llindhol@quicinc.com>,
sami.mujawar@arm.com, Gerd Hoffmann <kraxel@redhat.com>,
jiewen.yao@intel.com
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] About the feasibility of detaching Fdt16550SerialProtHookLib from ArmVirtPkg
Date: Mon, 16 Oct 2023 14:00:11 +0800 [thread overview]
Message-ID: <0f73ffd3-9889-3a62-2bcd-37ec51d07574@loongson.cn> (raw)
In-Reply-To: <33d7dbba-af9f-cb1d-6579-932ec9bbe16b@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Sorry, the last mail was misspelled, what I meant was: can we detaching
the Fdt16550SerialPortHookLib into OvmfPkg?
Thanks,
Chao
在 2023/10/16 10:58, Chao Li 写道:
>
> Hi Ard,
>
> I'm porting the LoongArch virt-machine to edk2. LoongArch virt-machine
> uses Fdt16550SerialPortHookLib to handle the UartBase, and the
> gEarly16550UartBaseAddressGuid is defined in ArmVirtPkg.dec.
>
> I think this library can be used in other Arch, like RISC-V LoongArch
> and so on, so can we feasibility this library into OvmfPkg?
>
> Hope to hear back from you.
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109621): https://edk2.groups.io/g/devel/message/109621
Mute This Topic: https://groups.io/mt/101989244/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: 2169 bytes --]
next prev parent reply other threads:[~2023-10-16 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 2:58 [edk2-devel] About the feasibility of detaching Fdt16550SerialProtHookLib from ArmVirtPkg Chao Li
2023-10-16 6:00 ` Chao Li [this message]
2023-10-16 7:47 ` Gerd Hoffmann
2023-10-16 8:03 ` Chao Li
2023-10-16 8:08 ` Gerd Hoffmann
2023-10-16 10:21 ` 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-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=0f73ffd3-9889-3a62-2bcd-37ec51d07574@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