From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Hauke Mehrtens" <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
"Rafał Miłecki" <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Dan Haab <dhaab-RSK6WAzFx3QAvxtiuMwx3w@public.gmane.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"moderated list:ARM PORT"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ARM: BCM5301X: Add DT for Luxul XAP-1510
Date: Thu, 5 May 2016 14:48:57 -0700 [thread overview]
Message-ID: <572BBFC9.1030800@gmail.com> (raw)
In-Reply-To: <572BBF6B.8030207-5/S+JYg5SzeELgA04lAiVw@public.gmane.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 <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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
--
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
prev parent reply other threads:[~2016-05-05 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 17:28 [PATCH] ARM: BCM5301X: Add DT for Luxul XAP-1510 Dan Haab
[not found] ` <1462296501-5209-1-git-send-email-dhaab-RSK6WAzFx3QAvxtiuMwx3w@public.gmane.org>
2016-05-04 18:53 ` Florian Fainelli
[not found] ` <572A453E.6010000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-04 22:36 ` Rafał Miłecki
2016-05-05 21:47 ` Hauke Mehrtens
[not found] ` <572BBF6B.8030207-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2016-05-05 21:48 ` Florian Fainelli [this message]
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=572BBFC9.1030800@gmail.com \
--to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dhaab-RSK6WAzFx3QAvxtiuMwx3w@public.gmane.org \
--cc=hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=zajec5-Re5JQEeQqe8AvxtiuMwx3w@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).