All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: edk2-devel@lists.sourceforge.net, Reza Jelveh <reza.jelveh@tuhh.de>
Cc: qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [edk2] license for binary drivers
Date: Wed, 06 Aug 2014 15:44:05 +0200	[thread overview]
Message-ID: <53E23125.5000009@redhat.com> (raw)
In-Reply-To: <53E2049E.4010106@redhat.com>

Il 06/08/2014 12:34, Laszlo Ersek ha scritto:
> So no, you can't ship an OVMF binary (or source tarball) that contains
> the FAT driver, bundled as part of the GPLv2 (+compatible) QEMU
> distribution, either in source or in binary form.

What Laszlo said is mostly my understanding too (IANAL etc.).

Just one thing: the GPL does allow you to "merely aggregate" the OVMF
binaries with QEMU sources or QEMU binaries; and a lawyer could also
tell you the if QEMU were to ship OVMF binaries in its tarball, it would
be mere aggregation.  It would then be allowed by the GPL.

I wouldn't disagree; the OVMF binaries are just data as far as QEMU is
concerned.

However, the non-free nature of the OVMF binaries mean that QEMU will
never ever ship OVMF binaries until the license is fixed for the
offending FAT driver.  Not only because we don't want to get into legal
minefields, but also because QEMU is free software and wants to keep its
distributed releases entirely free.

Paolo

  reply	other threads:[~2014-08-06 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140806074054.GF2170@masterlulz.local>
2014-08-06 10:34 ` [Qemu-devel] [edk2] license for binary drivers Laszlo Ersek
2014-08-06 13:44   ` Paolo Bonzini [this message]
2014-08-06 21:51     ` Andrew Fish
2014-08-06 22:22       ` Reza Jelveh
2014-08-07 12:53       ` Paolo Bonzini

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-all 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=53E23125.5000009@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=edk2-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=reza.jelveh@tuhh.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.