devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DT license
Date: Mon, 7 Jul 2014 11:29:54 +0100	[thread overview]
Message-ID: <20140707102954.GA2089@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131026222020.GX16735-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>

On Sat, Oct 26, 2013 at 11:20:20PM +0100, Russell King - ARM Linux wrote:
> Grant,
> 
> I'm seeing someone commenting on the GPLv2 license on the DT files.  This
> is probably something else which should've been discussed at the kernel
> summit.
> 
> I don't see much point to these being this restrictive: maybe GPLv2 and
> a.n.other license (3-clause BSD) would be a good idea.
> 
> Yes, technically it's a separate project from the kernel, but bear in
> mind that there's folks who would like to use the DT descriptions with
> something like OpenBSD.
> 
> It seems sensible to allow at least the stable stuff to become usable
> with other open OSes.

I didn't receive a reply to the above, and now this is becoming a
pressing matter because I'm about to start accepting patches from
others for the SolidRun DT files.

It is my intention to place the DT files for the SolidRun stuff under
the X11 license, and updates to them will only be accepted if submitted
under this license.

I also considered WTFPL, but I feel that WTFPL is too exposing for
warranty purposes.

The FSF indicate that the X11 license is compatible with GPLv2.

The reasoning there is to permit non-GPL projects (such as the BSDs) to
make use of the DT descriptions which are written for this hardware,
rather than forcing them to write their own - even though the main iMX
DT files may not be (yet) placed under such a permissive license.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
--
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

           reply	other threads:[~2014-07-07 10:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20131026222020.GX16735-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>]

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=20140707102954.GA2089@n2100.arm.linux.org.uk \
    --to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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).