[meta-freescale] [meta-fsl-arm][PATCH] add custom-licenses dir for freescale EULA
Lauren.Post at freescale.com
Thu Feb 5 07:37:30 PST 2015
We are discussing this offline.
Freescale is moving to a new license with same rights are current EULA but covers more Freescale product lines including i.MX and Layerscape. This transition will happen before Yocto Project 1.8 is released.
I'll upstream the new EULA once it is ready and this removes the requirement for multiple EULAs.
i.MX Yocto Project Team Lead
Freescale Trusted Advisor for licensing
From: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-bounces at yoctoproject.org] On Behalf Of Otavio Salvador
Sent: Thursday, February 05, 2015 9:21 AM
To: Luo Zhenhua-B19537
Cc: meta-freescale at yoctoproject.org
Subject: Re: [meta-freescale] [meta-fsl-arm][PATCH] add custom-licenses dir for freescale EULA
On Thu, Feb 5, 2015 at 1:08 PM, zhenhua.luo at freescale.com <zhenhua.luo at freescale.com> wrote:
> I agree to manage the license files in a unified manner.
> The EULA in fsl-arm layer includes both Freescale EULA content and some other 3rd party license content, Freescale-EULA only includes the Freescale EULA content.
Maybe it'd be better to split it out?
> Is there detailed description of the license whitelist mechanism? I am interested in whether it is applicable for LS1 and PPC packages which are under Freescale EULA or other proprietary license.
No; but I can support any improvement we may need on the technical side. I think the first thing we ought to do is to identify how to deal with the license and later adapt the code for it.
Otavio Salvador O.S. Systems
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
meta-freescale mailing list
meta-freescale at yoctoproject.org
More information about the meta-freescale