public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran via groups.io" <rebecca=os.amperecomputing.com@groups.io>
To: devel@edk2.groups.io, ardb@kernel.org
Cc: andrei.warkentin@intel.com, Rebecca Cran <rebecca@bsdio.com>,
	"quic_llindhol@quicinc.com" <quic_llindhol@quicinc.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH] Emulator/X86EmulatorDxe: Replace with MultiArchUefiPkg build
Date: Fri, 6 Sep 2024 09:39:41 -0600	[thread overview]
Message-ID: <8898585c-1aaf-469c-a876-a36721afadb4@os.amperecomputing.com> (raw)
In-Reply-To: <CAMj1kXHuOO1JiN9JDVCHwuyNdg8yGMLbg8GhyP3OBO0APh77Dg@mail.gmail.com>

On 9/6/2024 9:25 AM, Ard Biesheuvel via groups.io wrote:
> arm64 firmware? Or RISC-V? There are many more options now for native
> drivers on arm64, so I'd expect the relevance of this hack to diminish
> but I guess RISC-V is at a different point on this curve.

arm64. The big thing that's missing is support for PCIe graphics cards 
during boot: lots of people want to be able to see the splash screen and 
change settings without needing to connect to the BMC VGA port.

Currently that means we need an x86 emulator to load the optrom on the 
vast majority of cards.

> LGPL is more permissive, so the combined work cannot be used under the
> LGPL terms only under GPL (with the usual disclaimer of me not being a
> lawyer)
>
> Note that it doesn't really matter for edk2-non-osi as long as the
> LICENSE file is accurate.

That's my understanding too. My confusion is that Unicorn has two 
license files:

https://github.com/intel/unicorn-for-efi/blob/main/COPYING

https://github.com/intel/unicorn-for-efi/blob/main/COPYING.LGPL2

I don't know if that just means that parts are under the GPL and others 
the LGPL (which would still mean the combined project is GPL-licensed).

--

Rebecca



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120524): https://edk2.groups.io/g/devel/message/120524
Mute This Topic: https://groups.io/mt/108202804/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-09-06 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 22:32 [edk2-devel] [PATCH] Emulator/X86EmulatorDxe: Replace with MultiArchUefiPkg build Rebecca Cran
2024-09-01  8:05 ` Ard Biesheuvel via groups.io
2024-09-02  2:49   ` Chao Li
2024-09-06  5:41     ` Andrei Warkentin
2024-09-06  8:44       ` Chao Li
2024-09-06  5:32   ` Andrei Warkentin
2024-09-06 14:22     ` Rebecca Cran via groups.io
2024-09-06 15:25       ` Ard Biesheuvel via groups.io
2024-09-06 15:39         ` Rebecca Cran via groups.io [this message]
2024-09-02 16:45 ` Michael D Kinney
2024-09-02 21:21   ` Rebecca Cran

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=8898585c-1aaf-469c-a876-a36721afadb4@os.amperecomputing.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