public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, lichao@loongson.cn
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	 Leif Lindholm <quic_llindhol@quicinc.com>,
	sami.mujawar@arm.com, jiewen.yao@intel.com
Subject: Re: [edk2-devel] About the feasibility of detaching Fdt16550SerialProtHookLib from ArmVirtPkg
Date: Mon, 16 Oct 2023 09:47:28 +0200	[thread overview]
Message-ID: <n2gzcr4ahpw6agqbgdaj5qonbhsx6egkzypspm5obsgl5jktlm@56csqd543jks> (raw)
In-Reply-To: <33d7dbba-af9f-cb1d-6579-932ec9bbe16b@loongson.cn>

On Mon, Oct 16, 2023 at 10:58:29AM +0800, Chao Li wrote:
> 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?

Yes, OvmfPkg is the home for virtualization-related packages.  We moved
libs from ArmVirtPkg to OvmfPkg before so risc-v can easily share them.

take care,
  Gerd



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109622): https://edk2.groups.io/g/devel/message/109622
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]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2023-10-16  7:47 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
2023-10-16  7:47 ` Gerd Hoffmann [this message]
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=n2gzcr4ahpw6agqbgdaj5qonbhsx6egkzypspm5obsgl5jktlm@56csqd543jks \
    --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