Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755830AbaLWMWo (ORCPT ); Tue, 23 Dec 2014 07:22:44 -0500 Received: from vm1.sequanux.org ([188.165.36.56]:53015 "EHLO vm1.sequanux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751753AbaLWMWm (ORCPT ); Tue, 23 Dec 2014 07:22:42 -0500 Date: Tue, 23 Dec 2014 13:22:33 +0100 From: Simon Guinot To: Arnd Bergmann Cc: linux-arm-kernel@lists.infradead.org, Jason Cooper , Lior Amsalem , Andrew Lunn , Heikki Krogerus , Nadav Haklai , Greg Ungerer , Benoit Masson , Lorenzo Pieralisi , Tawfik Bayouk , Ezequiel Garcia , Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= , Sebastian Hesselbarth , "klightspeed @ killerwolves . net" , Nobuhiro Iwamatsu , Arnaud Ebalard , Gregory CLEMENT , Nobuhiro Iwamatsu , Marcin Wojtas , Florian Fainelli , Simon Baatz , Thomas Petazzoni , Ryan Press , linux-kernel@vger.kernel.org, Philipp Zabel , Willy Tarreau Subject: Re: [PATCH 00/27] ARM: mvebu: armada-*: Relicense the device tree under GPLv2+/X11 Message-ID: <20141223122233.GR19261@kw.sim.vm.gnt> References: <54930BBC.4060602@free-electrons.com> <20141221235000.GC28117@titan.lakedaemon.net> <20141222112933.GK19261@kw.sim.vm.gnt> <6219619.yRPYbqr6Sm@wuerfel> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Sosn/fv6aiTyEgxl" Content-Disposition: inline In-Reply-To: <6219619.yRPYbqr6Sm@wuerfel> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sosn/fv6aiTyEgxl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 22, 2014 at 10:14:32PM +0100, Arnd Bergmann wrote: > On Monday 22 December 2014 12:29:33 Simon Guinot wrote: > > On Sun, Dec 21, 2014 at 06:50:00PM -0500, Jason Cooper wrote: > > > On Fri, Dec 19, 2014 at 07:16:16PM +0100, Simon Guinot wrote: > > > > > > Especially none of the dove files have a license. > > > > >=20 > > > > > Yes, we'll cross that bridge when we get there. I suspect it the= n falls > > > > > under the over-arching license of the project. Regardless, we'll= still > > > > > need Acks from all contributors. > > > >=20 > > > > Hi Jason, > > > >=20 > > > > What is the problem with keeping the LaCie DTS files under GPLv2+ o= nly ? > > >=20 > > > Converting armada-* to dual license is just a small part of the > > > overarching effort to convert *all* the devicetree files to dual > > > license. So, eventually, we'll be doing the same with kirkwood, dove > > > and orion5x dts{i} files. Perhaps even during this merge window. > > >=20 > > > In the long term, we're attempting to provide one neutral place [1] f= or > > > the bootloaders and kernels to pull devicetrees from and contribute > > > changes back to. > >=20 > > OK, let's see if I understand correctly. > >=20 > > If I don't agree with the GPLv2+/x11 relicensing, then support for > > almost all the LaCie boards will be removed from the Linux kernel (maybe > > during the next merge window) ? Is that correct ? >=20 > Definitely not during the next merge window. Eventually the plan is > to remove *all* dts files from the kernel, but we're a long way > away from that. >=20 > There is already a mirror of the dts files at > http://xenbits.xen.org/gitweb/?p=3Dpeople/ianc/device-tree-rebasing.git;a= =3Dsummary > which is hosting files that are meant to be shared with Xen, which is > also under the GPL, and supports a lot of the same hardware that Linux > supports, but also depends on passing the correct (modified) dtb blobs > to the Dom0 kernel. >=20 > The current setup works ok for Xen, but occasionally there are requests > for having the files shared more broadly, e.g. with FreeBSD and with boot > loaders that might be non-GPL but are used to boot Linux and that want > to ship with a default dtb for a platform they run on. Minus some details you just provided, that's what I understood in a first place. >=20 > > Since all the LaCie boards DTS are at least based on my work (except for > > the Orion ED Mini v2), I think there is 12 files concerned here. See the > > command output: grep -l lacie *.dts | wc -l. > >=20 > > The oldest of this boards have been supported by the Linux kernel since > > the 2.6.32 release. Also some of this boards are still widely used... > >=20 > > You know, it is quite a statement you are sending here: The GPLv2+ > > licences are not good enough to get an ARM-based board supported by > > the Linux kernel, while it has always been the case until now. Are all > > the maintainers SoC, ARM SoC, ARM and Linux well aligned with that ? >=20 > I think you just misunderstood. Jason said: "Regrettably, we'll have to revert Simon's dts contributions". This words changed my understanding. Then, you confirm I don't have to worry about that ? >=20 > > Is there any way we can keep the LaCie DTS files licenced under GPLv2+ > > _and_ still distributed with the others. Anyone would be free to choose > > to use them (or not), in respect of the licence terms. >=20 > What I suspect will happen is that we end up with multiple repositories > for dts files, e.g. one that contains all files that are GPL-compatible > and another one that contains the subset that is licensed under more > permissive licenses such as the X11 or some BSD license. I don't see > a reason for Linux to stop supporting the former, but it would be nice > to have a larger shared subset. I think it would be indeed a good idea to have a repository with some licence separations. Thanks for the clarifications. Simon --Sosn/fv6aiTyEgxl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlSZXokACgkQgtp0PDeOcDqjjACdF7XLJTAEO9/umIgAE6Mwd5qi 2kcAoJQgAdgfOVB0oBkag9SBdpBrYJAu =WQXL -----END PGP SIGNATURE----- --Sosn/fv6aiTyEgxl-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/