From: Allen Martin <amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/2] tegrarcm: License update for miniloader files
Date: Mon, 17 Jun 2013 22:42:24 -0700 [thread overview]
Message-ID: <20130618054224.GA11269@badger> (raw)
In-Reply-To: <51BFDD56.7060302-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Mon, Jun 17, 2013 at 09:08:54PM -0700, Stephen Warren wrote:
> On 06/17/2013 09:25 PM, Allen Martin wrote:
> > This changes the license under which the miniloader files are
> > distributed to the same license used for the binary portions of the
> > Tegra L4T distribution. This should hopefully make the license more
> > palatable to distributions.
> >
> > Also changed the description to say that the license applies to all
> > files in the miniloader directory instead of individually listing the
> > files. This should hopefully prevent it from becoming stale.
>
> This still seems rather over-complex:-(
>
> > +2.1.1 Rights. Customer may install and use one copy of the SOFTWARE
> > +on a single computer, and except for making one back-up copy of
> > +the Software, may not otherwise copy the SOFTWARE. This LICENSE
> > +of SOFTWARE may not be shared or used concurrently on different
> > +computers.
> > +
> > +2.1.2 Linux/FreeBSD Exception. Notwithstanding the foregoing terms
> > +of Section 2.1.1, SOFTWARE designed exclusively for use on the Linux or
> > +FreeBSD operating systems, or other operating systems derived from the
> > +source code to these operating systems, may be copied and redistributed,
> > +provided that the binary files thereof are not modified in any way
> > +(except for unzipping of compressed files).
>
> Given that 2.1.2 appears to override 2.1.1 in the context of this SW,
> why even include 2.1.1? I know we're re-using the L4T license here, but
> I'd really prefer to just use something plain and simple that doesn't
> include irrelevant lawyer-speak.
>
> > +No Rental. Customer may not rent or lease the SOFTWARE to someone
> > +else.
>
> Isn't that going to cause problems for distros? IANAL, but that doesn't
> sound GPL compatible, since it's an additional restriction that I don't
> think the GPL imposes.
This probably requires coordination with L4T since it's the same
license file, and we should keep them the same if at all possible.
I'm going to defer this license change to version 1.5 and push the
other patches out that you acked since ChromeOS is waiting on the SPI
fix.
-Allen
--
nvpublic
next prev parent reply other threads:[~2013-06-18 5:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1371525937-2713-1-git-send-email-amartin@nvidia.com>
[not found] ` <1371525937-2713-1-git-send-email-amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-18 3:25 ` [PATCH 2/2] tegrarcm: License update for miniloader files Allen Martin
[not found] ` <1371525937-2713-2-git-send-email-amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-18 4:08 ` Stephen Warren
[not found] ` <51BFDD56.7060302-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-18 5:42 ` Allen Martin [this message]
2013-06-18 8:16 ` Marc Dietrich
2013-06-18 3:30 ` [PATCH 1/2] tegrarcm: Move miniloader files to "miniloader" subdir Allen Martin
2013-06-18 4:10 ` Stephen Warren
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=20130618054224.GA11269@badger \
--to=amartin-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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