All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux-arm@myspectrum.nl (Jeroen Hofstee)
To: linux-arm-kernel@lists.infradead.org
Subject: Device Tree Blob (DTB) licence
Date: Sat, 30 May 2015 21:59:26 +0200	[thread overview]
Message-ID: <556A169E.8030909@myspectrum.nl> (raw)
In-Reply-To: <1432289148.5304.58.camel@opteya.com>

Hi,

On 22-05-15 12:05, Yann Droneaud wrote:
> Le mardi 05 mai 2015 ? 11:41 -0500, Rob Herring a ?crit :
>> On Tue, May 5, 2015 at 5:05 AM, Yann Droneaud <ydroneaud@opteya.com>
>> wrote:
>>> 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.
>> By default yes, but we've been steering people to dual license them
>> GPL/BSD.
>>
>

obviously these files should be reusable. If there is a license issue
with that it should be fixed. cc-ing freebsd-arm at freebsd.org.

I am not a lawyer,

Jeroen

WARNING: multiple messages have this Message-ID (diff)
From: Jeroen Hofstee <linux-arm@myspectrum.nl>
To: Yann Droneaud <ydroneaud@opteya.com>,
	Rob Herring <robherring2@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	freebsd-arm@freebsd.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Device Tree Blob (DTB) licence
Date: Sat, 30 May 2015 21:59:26 +0200	[thread overview]
Message-ID: <556A169E.8030909@myspectrum.nl> (raw)
In-Reply-To: <1432289148.5304.58.camel@opteya.com>

Hi,

On 22-05-15 12:05, Yann Droneaud wrote:
> Le mardi 05 mai 2015 à 11:41 -0500, Rob Herring a écrit :
>> On Tue, May 5, 2015 at 5:05 AM, Yann Droneaud <ydroneaud@opteya.com>
>> wrote:
>>> 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.
>> By default yes, but we've been steering people to dual license them
>> GPL/BSD.
>>
>

obviously these files should be reusable. If there is a license issue
with that it should be fixed. cc-ing freebsd-arm@freebsd.org.

I am not a lawyer,

Jeroen
_______________________________________________
freebsd-arm@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"

WARNING: multiple messages have this Message-ID (diff)
From: Jeroen Hofstee <linux-arm@myspectrum.nl>
To: Yann Droneaud <ydroneaud@opteya.com>,
	Rob Herring <robherring2@gmail.com>
Cc: freebsd-arm@freebsd.org,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Device Tree Blob (DTB) licence
Date: Sat, 30 May 2015 21:59:26 +0200	[thread overview]
Message-ID: <556A169E.8030909@myspectrum.nl> (raw)
In-Reply-To: <1432289148.5304.58.camel@opteya.com>

Hi,

On 22-05-15 12:05, Yann Droneaud wrote:
> Le mardi 05 mai 2015 à 11:41 -0500, Rob Herring a écrit :
>> On Tue, May 5, 2015 at 5:05 AM, Yann Droneaud <ydroneaud@opteya.com>
>> wrote:
>>> 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.
>> By default yes, but we've been steering people to dual license them
>> GPL/BSD.
>>
>

obviously these files should be reusable. If there is a license issue
with that it should be fixed. cc-ing freebsd-arm@freebsd.org.

I am not a lawyer,

Jeroen

  parent reply	other threads:[~2015-05-30 19:59 UTC|newest]

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

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=556A169E.8030909@myspectrum.nl \
    --to=linux-arm@myspectrum.nl \
    --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 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.