Re: [Xen-devel] [PATCH v4 02/21] acpi: Prevent GPL-only code from seeping into non-GPL binaries

[Lars Kurth <lars.kurth@xxxxxxxxxx>]

On 20/09/2016 01:19, "Boris Ostrovsky" <boris.ostrovsky@xxxxxxxxxx> wrote:

>Some code (specifically, introduced by commit 801d469ad ("[HVM] ACPI
>support patch 3 of 4: ACPI _PRT table.")) has only been licensed under
>GPLv2. We want to prevent this code from showing up in non-GPL
>binaries which might become possible after we make ACPI builder code
>available to users other than hvmloader.
>
>There are two pieces that we need to be careful about:
>(1) A small piece of code in dsdt.asl that implements _PIC method
>(2) A fragment of ASL generator in mk_dsdt.c that describes PCI
>    interrupt routing.
>
>The cleanest way to deal with this seems to be taking generatedi ASL
>chunk from (2), adding it to dsdt.asl and keeping dsdt.asl GPL-only.

...

>diff --git a/tools/firmware/hvmloader/acpi/gpl/COPYING
>b/tools/firmware/hvmloader/acpi/gpl/COPYING
>new file mode 100644
>index 0000000..8dfdf61
>--- /dev/null
>+++ b/tools/firmware/hvmloader/acpi/gpl/COPYING
>@@ -0,0 +1,5 @@
>+Unlike files in the directory above that are licensed under GNU Lesser
>+General Public License version 2.1, files here are licensed under GNU
>+General Public License version 2.
>+
>+A copy of this license can be obtained at <http://www.gnu.org/licenses/>

Add the following:

INBOUND LICENSE

Contributions to this directory are made under the LGPLv2.1 *only* as
described
in the COPYING file of the parent directory. As LGPLv2.1 is compatible
with the
GPLv2, the resulting file is GPLv2 when seen as a whole.

The intention of this inbound license, is to avoid having to ask
subsequent 
contributors to this directory for permission to change the license from
GPLv2
to LGPLv2.1, once we get permission from the remaining copyright holders
of 
this directory to change the license to LGPLv2.1.

Note: The only outstanding permission required to re-license this
directory to
LGPLv2.1 is from Lenovo.


Regards
Lars


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel