public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: Pedro Falcato <pedro.falcato@gmail.com>,
	devel@edk2.groups.io, rebecca@os.amperecomputing.com
Cc: Chao Li <lichao@loongson.cn>,
	andrei.warkentin@intel.com, Ard Biesheuvel <ardb@kernel.org>,
	"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: Tue, 22 Oct 2024 20:20:20 -0600	[thread overview]
Message-ID: <5da6e748-a2da-44dc-9710-82be5d1599a3@bsdio.com> (raw)
In-Reply-To: <CAKbZUD2PGnuhfNbm18u3AG8mFK+yAivh8tOs3CUigafNVKyLew@mail.gmail.com>

On 10/22/24 5:44 PM, Pedro Falcato wrote:

> 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").


If loading into the same address space is the issue, wouldn't GRUB being 
loaded infect the firmware too?

My point was that UEFI firmware could be considered a filesystem, with 
the EmulatorDxe.efi simply being on the same filesystem as the other 
drivers. That's opposed to being linked into the same binary, which is 
clearly a GPL violation.


-- 
Rebecca



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



  parent reply	other threads:[~2024-10-23  2:20 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
2024-10-23  2:08             ` Chao Li
2024-10-23  2:20             ` Rebecca Cran [this message]
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=5da6e748-a2da-44dc-9710-82be5d1599a3@bsdio.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