linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ydroneaud@opteya.com (Yann Droneaud)
To: linux-arm-kernel@lists.infradead.org
Subject: Device Tree Blob (DTB) licence
Date: Tue, 05 May 2015 12:05:15 +0200	[thread overview]
Message-ID: <1430820315.19516.26.camel@opteya.com> (raw)

Hi,

I believe Device Tree Blob (.dtb file) built from kernel's Device Tree 
Sources (.dts, which #include .dtsi, which #include .h) using Device 
Tree Compiler (dtc) are covered by GNU General Public Licence v2 
(GPLv2), but cannot find any reference.

As most .dtsi in arch/arm/boot/dts/ are covered by GPLv2, and,
as most .h in include/dt-bindings/ are also covered by GPLv2,
the source code is likely covered by GPLv2.

Then this source code is translated in a different language (flattened 
device tree), so the resulting translation is also likely covered by 
GPLv2.

So, when I'm proposed to download a .dtb file from a random vendor,
can I require to get the associated source code ?

Anyway, for a .dtb file generated from kernel sources, it's rather 
painful to look after all .dts, .dtsi, .h, to find what kind of 
licences are applicables, as some are covered by BSD, dual licensed 
(any combination of X11, MIT, BSD, GPLv2).

Regards.

-- 
Yann Droneaud
OPTEYA

             reply	other threads:[~2015-05-05 10:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 10:05 Yann Droneaud [this message]
2015-05-05 16:41 ` Device Tree Blob (DTB) licence Rob Herring
2015-05-22 10:05   ` Yann Droneaud
2015-05-22 16:26     ` Rob Herring
2015-05-28 12:31       ` Enrico Weigelt, metux IT consult
2015-05-22 19:27     ` Yann Droneaud
2015-05-25  7:14       ` Rob Landley
2015-05-25 20:04         ` Willy Tarreau
2015-05-28 12:32         ` Enrico Weigelt, metux IT consult
2015-05-28 13:34           ` Russell King - ARM Linux
2015-05-28 16:52             ` Enrico Weigelt, metux IT consult
2015-05-29  6:47               ` Willy Tarreau
2015-05-29 11:35                 ` Enrico Weigelt, metux IT consult
2015-05-29 22:16                   ` David Lang
2015-05-30 15:28                     ` Geert Uytterhoeven
2015-06-01 13:12                     ` One Thousand Gnomes
2015-06-01 15:19                       ` Warner Losh
2015-05-29  3:31           ` Rob Landley
2015-05-29 15:10             ` Enrico Weigelt, metux IT consult
2015-05-29 22:21               ` David Lang
2015-05-30  2:43               ` Jean-Christophe PLAGNIOL-VILLARD
2015-06-22 12:57         ` Pavel Machek
2015-05-30 19:59     ` Jeroen Hofstee
2015-05-31  7:12       ` Warner Losh

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=1430820315.19516.26.camel@opteya.com \
    --to=ydroneaud@opteya.com \
    --cc=linux-arm-kernel@lists.infradead.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).