All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ann Thornton <Ann.Thornton@freescale.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Lauren Post <Lauren.Post@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH] fsl-eula-unpack: deploy Freescale EULA
Date: Mon, 8 Jun 2015 09:09:03 -0500	[thread overview]
Message-ID: <5575A1FF.6060603@freescale.com> (raw)
In-Reply-To: <CAP9ODKoswM4MY08e-xZyfArD-=e6AZJhXSTXLciBGTGESo6c4A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]


I think you are misunderstanding what this says.  It is saying that the 
licenses in the software override this.  So the GPL licensed code is 
still GPL, etc.

Ann

On 6/8/2015 8:01 AM, Otavio Salvador wrote:
> Dear Lauren,
>
> On Thu, Jun 4, 2015 at 2:27 PM, Lauren Post <Lauren.Post@freescale.com> wrote:
> ...
>> All software is subject to agreement to, and compliance with, Freescale's
>> End User License Agreement.   To have the right to use these binaries in
>> your images, you must read and accept the following terms.  If there are
>> conflicting terms embedded in the software, the terms embedded in the
>> Software will control.
> ...
>
> I completely disagree with the change proposed by your lawyer. The
> statement seems completely wrong to me.
>
> When we use the "all" word this states that Freescale EULA overrides
> the license terms of:
>
> Linux kernel - GPL-2.0
> Qt5 - LGPL-3.0 / commercial
> …
>
> and Freescale has no right to do so. The proposed text put Freescale
> at risk of license agreement glitch as when it is said "If there are
> conflicting terms embedded in the software, the terms embedded in the
> Software will control." it opens the door for someone to make a GPL
> application and contaminate EULA covered binaries (i.e Vivante's
> ones), just by linking at them and stating their license "controls"
> the license terms.  It is clear that the lawyer is underestimating the
> complexity involved here.
>
> The text in use, nowadays, in the setup-environment:
>
> "Some BSPs depend on libraries and packages which are covered by Freescale's
> End User License Agreement (EULA). To have the right to use these binaries in
> your images, you need to read and accept the following..."
>
> Makes clear that it is user/customer duty to inspect the EULA and
> check if it is possible to agree with it, it makes clear libraries and
> packages might be under this license and its his/her duty to verify
> those.
>
> Regards,
>


-- 
Ann Thornton

/Microcontrollers Software and Applications
Freescale Semiconductors
email: Ann.Thornton@freescale.com/

[-- Attachment #2: Type: text/html, Size: 2894 bytes --]

  reply	other threads:[~2015-06-08 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  8:55 [PATCH] fsl-eula-unpack: deploy Freescale EULA Stefan Christ
2015-06-03 14:13 ` Lauren Post
2015-06-03 14:30   ` Otavio Salvador
2015-06-03 14:56     ` Ann Thornton
2015-06-03 16:15       ` Otavio Salvador
2015-06-03 16:46         ` Eric Nelson
2015-06-03 17:19           ` Lauren Post
2015-06-03 18:22             ` Daiane Angolini
2015-06-04 16:34               ` Ann Thornton
2015-06-04 17:27                 ` Lauren Post
2015-06-08 13:01                   ` Otavio Salvador
2015-06-08 14:09                     ` Ann Thornton [this message]
2015-06-08 15:06                       ` Otavio Salvador
2015-06-05  7:25           ` Stefan Christ
2015-06-05 21:06             ` Ann Thornton

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=5575A1FF.6060603@freescale.com \
    --to=ann.thornton@freescale.com \
    --cc=Lauren.Post@freescale.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.