From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757974AbcEEVtH (ORCPT ); Thu, 5 May 2016 17:49:07 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:36102 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757449AbcEEVtE (ORCPT ); Thu, 5 May 2016 17:49:04 -0400 Subject: Re: [PATCH] ARM: BCM5301X: Add DT for Luxul XAP-1510 To: Hauke Mehrtens , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= References: <1462296501-5209-1-git-send-email-dhaab@luxul.com> <572A453E.6010000@gmail.com> <572BBF6B.8030207@hauke-m.de> Cc: Dan Haab , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:ARM PORT" , open list From: Florian Fainelli Message-ID: <572BBFC9.1030800@gmail.com> Date: Thu, 5 May 2016 14:48:57 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <572BBF6B.8030207@hauke-m.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/05/16 14:47, Hauke Mehrtens wrote: > On 05/05/2016 12:36 AM, Rafał Miłecki wrote: >> On 4 May 2016 at 20:53, Florian Fainelli wrote: >>> On 03/05/16 10:28, Dan Haab wrote: >>>> Luxul XAP-1510 is an AP device based on BCM4708 SoC. It uses flash >>>> memory connected to the SPI controller. >>> >>> Looks fine, except one nit: >>> >>>> diff --git a/arch/arm/boot/dts/bcm4708-luxul-xap-1510.dts b/arch/arm/boot/dts/bcm4708-luxul-xap-1510.dts >>>> new file mode 100644 >>>> index 0000000..f4460b5 >>>> --- /dev/null >>>> +++ b/arch/arm/boot/dts/bcm4708-luxul-xap-1510.dts >>>> @@ -0,0 +1,67 @@ >>>> +/* >>>> + * Broadcom BCM470X / BCM5301X ARM platform code. >>>> + * DTS for Luxul XAP-1510 >>>> + * >>>> + * Copyright 2015 Luxul Inc. >>>> + * >>>> + * Licensed under the GNU/GPL. See COPYING for details. >>> >>> The ARM SoC maintainer have been asking to utilize a license which is >>> also BSD compatible, so something along the lines of this one: >>> >>> arch/arm/boot/dts/bcm911360k.dts >>> >>> Do you mind respining the patch to include that kind of license header? >> >> I wasn't aware of this neither. Shall we re-license existing DTS files >> as well? I'm fine with changing them to BSD compatible. >> >> I'm a bit confused by using BSD license only. Kernel is licensed under >> GNU GPL version 2 and if there are some BSD compatible modules, they >> use dual licensing model (BSD/GPL). Shouldn't we use BSD/GPL in DTS >> files as well then? >> > > As far as I understand the License part you can take code which is > licensed under BSD license and use it in GPL code because you can comply > with the BSD license and also handle it in a way to be GPL compliant at > the same time. You can also make a change to BSD code and license this > change under the GPL, then the complete code (the old one + your change) > is now GPL. > > Are the device tree files licensed under BSD license to make it easier > to integrate them into a proprietary boot loader or what is the purpose? Yes, there could be that, or just making the license compatible with other OSes like FreeBSD for instace. -- Florian