From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, rebecca@os.amperecomputing.com
Cc: Chao Li <lichao@loongson.cn>,
andrei.warkentin@intel.com, Ard Biesheuvel <ardb@kernel.org>,
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: Wed, 23 Oct 2024 00:44:46 +0100 [thread overview]
Message-ID: <CAKbZUD2PGnuhfNbm18u3AG8mFK+yAivh8tOs3CUigafNVKyLew@mail.gmail.com> (raw)
In-Reply-To: <c3e6d0e2-7b9c-4dbd-8f91-3db837e8d53a@os.amperecomputing.com>
On Tue, Oct 22, 2024 at 11:29 AM Rebecca Cran via groups.io
<rebecca=os.amperecomputing.com@groups.io> wrote:
>
> On 10/22/2024 2:48 AM, Chao Li wrote:
>
> > I see the final licence in non-osi is GPL2.0, so it that allowed for
> > some people build the EmulatorDxe.efi into their FW and release it?
>
> I believe it is allowed because tools like Fiano allow you to remove
> drivers such as EmulatorDxe from the firmware image.
I don't understand what you mean? nor do I understand the question.
Mandatory IANAL.
You can build whatever GPL-violating contraption as long as you don't
distribute it. If you do, you need to comply with the terms of the
license.
FWIW, GNU seems to think merely including this module would be a GPL
violation (https://www.gnu.org/licenses/gpl-faq.html#MereAggregation,
see the mention of running together in a shared address space), and
thus all your firmware would potentially need to be distributed under
the GPL's terms.
Ard's old version seems to only be LGPL and thus you'd only need to
comply with the LGPL's terms for that specific module (there's no
"virality").
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120657): https://edk2.groups.io/g/devel/message/120657
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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-10-22 23:45 UTC|newest]
Thread overview: 17+ 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
2024-10-22 8:48 ` Chao Li
2024-10-22 10:29 ` Rebecca Cran via groups.io
2024-10-22 23:44 ` Pedro Falcato [this message]
2024-10-23 2:08 ` Chao Li
2024-10-23 2:20 ` Rebecca Cran
2024-10-23 11:10 ` Pedro Falcato
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=CAKbZUD2PGnuhfNbm18u3AG8mFK+yAivh8tOs3CUigafNVKyLew@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