public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel via groups.io" <ardb=kernel.org@groups.io>
To: Rebecca Cran <rebecca@os.amperecomputing.com>
Cc: devel@edk2.groups.io, 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 17:25:17 +0200	[thread overview]
Message-ID: <CAMj1kXHuOO1JiN9JDVCHwuyNdg8yGMLbg8GhyP3OBO0APh77Dg@mail.gmail.com> (raw)
In-Reply-To: <1b111e7f-7153-474b-8656-53ce289abb2a@os.amperecomputing.com>

On Fri, 6 Sept 2024 at 16:22, Rebecca Cran
<rebecca@os.amperecomputing.com> wrote:
>
> Hi Andrei,
>
>
> I've been talking to a few people about X86EmulatorPkg and their
> experience with it hasn't been positive: apparently there are lots of
> cases where it's failed to work (i.e. caused crashes) which is why it's
> not been more widely used.
>

Interestingly, since the original release in 2017, around which I did
receive some feedback, I have not received a single piece of feedback
(positive or negative) ever since.

So while I'm happy that there is a better solution for them now, I'm
kind of annoyed by the fact that not a single person ever bothered to
report any issue that they encountered while using the original
version.

> Since suggesting they try MultiArchUefiPkg they've said it's working
> much better, and in fact some people have proceeded with enabling it in
> their firmware.
>

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.

>
> I'm a bit confused about the licensing of MultiArchUefiPkg given the
> license file says it's LGPL while it uses the GPL-licensed Unicorn library.
>
> Does that mean the overall licensing for it will be GPL?
>

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.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120523): https://edk2.groups.io/g/devel/message/120523
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:25 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 [this message]
2024-09-06 15:39         ` Rebecca Cran via groups.io
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=CAMj1kXHuOO1JiN9JDVCHwuyNdg8yGMLbg8GhyP3OBO0APh77Dg@mail.gmail.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