From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
Karsten Merker <merker-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts
Date: Tue, 2 Sep 2014 17:24:52 +0100 [thread overview]
Message-ID: <20140902162452.GS30401@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5405D74B.8090409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, Sep 02, 2014 at 04:42:19PM +0200, Hans de Goede wrote:
> Hi,
>
> On 09/02/2014 02:51 PM, Maxime Ripard wrote:
> > On Tue, Sep 02, 2014 at 02:35:18PM +0200, Hans de Goede wrote:
> >>> So I guess like Chen-Yu suggested that we should change the license of
> >>> the DTSI first, and then the DTS. Otherwise, it wouldn't work very
> >>> well, I guess you can't really relicense a GPL-only file.
> >>
> >> IANAL, but mixing MIT (which I suggest use as the other license) and GPL
> >> files in one binary (the generated dtb file) is fine AFAIK, this happens
> >> all the time. The resulting binary is simple GPL licensed. So it would
> >> make sense to start with dual licensing new boards right away even before
> >> the dtsi has been relicensed. It won't make any practical difference
> >> until the dtsi is relicensed, but it means less work later on.
> >
> > So you're allowed to licence derivative work of a GPL-licenced file
> > under both the GPL and another licence?
>
> Since the board files do not start as copies of the dtsi file, but
> merely include it they are not derivative (IANAL), the resulting
> dtb file however very much is and as such is GPL only.
I'd also agree with the second half of what you said.
Let's take an example. If a .dts file is licensed GPL and X11, but
a .dtsi it includes is licensed under the GPL, then the resulting
binary is definitely GPL-only - no questions asked.
If all the .dts and .dtsi files which are used to generate the .dtb
become licensed under the GPL and X11 licenses, then the resulting
.dtb itself becomes dual licensed.
If a .dtsi file is licensed under GPL and X11, but the .dts file is
only under the GPL, the result is GPL-only.
So, it's like a bitwise AND, with each license type being an
individual bit.
The first half is a more risky claim to make though - is the .dts file
itself something that could have been developed without the .dtsi?
Given that most .dts files reference things in the .dtsi files, I
believe the answer to that is no - which makes the .dts file a
derivative of the .dtsi.
What that would seem to imply is that the .dts files can't be dual
licensed until the .dtsi files it uses are dual licensed.
So, the "safe" approach here is to get the .dtsi files dual-licensed
first. :)
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-02 16:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:20 Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts Karsten Merker
[not found] ` <20140731192016.GA6869-Hlt6eto4P0pdWf7zwHaZWbNAH6kLmebB@public.gmane.org>
2014-08-03 13:04 ` Maxime Ripard
2014-08-03 17:59 ` Arnd Bergmann
[not found] ` <201408031959.27607.arnd-r2nGTMty4D4@public.gmane.org>
2014-08-04 19:25 ` Maxime Ripard
2014-08-04 21:23 ` Russell King - ARM Linux
[not found] ` <20140804212317.GL30282-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-08-05 8:06 ` Arnd Bergmann
2014-08-07 13:20 ` Maxime Ripard
2014-09-02 10:22 ` Maxime Ripard
2014-09-02 10:40 ` Russell King - ARM Linux
[not found] ` <20140902104002.GN30401-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-09-02 11:54 ` Chen-Yu Tsai
2014-09-02 12:27 ` Maxime Ripard
2014-09-02 12:35 ` Hans de Goede
[not found] ` <5405B986.2080407-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-02 12:51 ` Maxime Ripard
2014-09-02 13:02 ` Arnd Bergmann
2014-09-02 13:37 ` Russell King - ARM Linux
[not found] ` <20140902133713.GR30401-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-09-02 16:52 ` Russell King - ARM Linux
2014-09-02 14:42 ` Hans de Goede
[not found] ` <5405D74B.8090409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-02 15:18 ` Maxime Ripard
2014-09-02 16:24 ` Russell King - ARM Linux [this message]
2014-08-05 8:01 ` Hans de Goede
2014-08-05 8:02 ` Hans de Goede
2014-08-03 20:41 ` Russell King - ARM Linux
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=20140902162452.GS30401@n2100.arm.linux.org.uk \
--to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=merker-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).