From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19719 invoked by alias); 4 Dec 2013 12:08:34 -0000 Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org Received: (qmail 19707 invoked by uid 89); 4 Dec 2013 12:08:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_NEUTRAL,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: gateway15.websitewelcome.com Received: from Unknown (HELO gateway15.websitewelcome.com) (69.56.148.24) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Dec 2013 12:08:31 +0000 Received: by gateway15.websitewelcome.com (Postfix, from userid 5007) id 4F4F11F34F958; Wed, 4 Dec 2013 06:08:24 -0600 (CST) Received: from ham07.websitewelcome.com (unknown [192.185.0.198]) by gateway15.websitewelcome.com (Postfix) with ESMTP id 2E51D1F34F918 for ; Wed, 4 Dec 2013 06:08:24 -0600 (CST) Received: by ham07.websitewelcome.com (Postfix, from userid 500) id 639B646000A; Wed, 4 Dec 2013 06:08:23 -0600 (CST) X-Spam-Flag2999: NO X-Spam-Level2999: X-Spam-Status2999: "No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham version=3.3.1 Received: from montecarlo.websitewelcome.com (montecarlo.websitewelcome.com [192.185.12.42]) by ham07.websitewelcome.com (Postfix) with ESMTP id 53A5346000A for ; Wed, 4 Dec 2013 06:08:21 -0600 (CST) Received: from [213.115.176.230] (port=40988 helo=[192.168.0.232]) by montecarlo.websitewelcome.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from ) id 1VoBFd-0002iT-8k; Wed, 04 Dec 2013 06:08:21 -0600 Message-ID: <529F1B33.1020603@siva.com.mk> Date: Wed, 04 Dec 2013 12:08:00 -0000 From: =?UTF-8?B?IklsaWphIEtvY2hvIFvQmNC70LjRmNCwINCa0L7Rh9C+XSI=?= User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: ecos-maintainers@ecos.sourceware.org CC: Michael Jones , Jonathan Larmour Subject: Re: Copyright and maintainability question for new ARM Cortex A9 HAL References: <77A01081-8A89-4D60-B7B1-78D774946EC6@linear.com> <522A97B3.4060607@eCosCentric.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BWhitelist: no X-Source-Sender: ([192.168.0.232]) [213.115.176.230]:40988 X-Source-Auth: ilijak+siva.mk X-Email-Count: 3 X-Source-Cap: c2l2YW1rO2JpYmltYW47bW9udGVjYXJsby53ZWJzaXRld2VsY29tZS5jb20= X-IsSubscribed: yes X-SW-Source: 2013-12/txt/msg00000.txt.bz2 Maintainers, The licence below is practically "3 clause BSD". Since we already have BSD-licenced code in our tree, I propose that we accept Freescale's code published under this licence. Any remarks? Ilija On 07.09.2013 15:39, Michael Jones wrote: > Jonathan, > > The files have the following copyright. They do not refer to any license. > > I find the second redistribution clause a nuisance. It means if you make an app or library and distribute, you have to reproduce the copyright notice. Just how do you do that with an end application? > > Mike > > /* > * Copyright (c) 2013, Freescale Semiconductor, Inc. > * All rights reserved. > * > * Redistribution and use in source and binary forms, with or without modification, > * are permitted provided that the following conditions are met: > * > * o Redistributions of source code must retain the above copyright notice, this list > * of conditions and the following disclaimer. > * > * o Redistributions in binary form must reproduce the above copyright notice, this > * list of conditions and the following disclaimer in the documentation and/or > * other materials provided with the distribution. > * > * o Neither the name of Freescale Semiconductor, Inc. nor the names of its > * contributors may be used to endorse or promote products derived from this > * software without specific prior written permission. > * > * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND > * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED > * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE > * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR > * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES > * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; > * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON > * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT > * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS > * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > */ > > > > On Sep 6, 2013, at 9:04 PM, Jonathan Larmour wrote: > >> On 05/09/13 04:52, Michael Jones wrote: >>> The status is: >>> >>> - Project not registered yet >> That's not an issue. Projects don't need to be registered. >> >>> - Uses Freescale SDK macros >>> - Uses Freescale SDK code for MMU, GIC, etc >> Okay, the most important thing we need to know is the license for that >> Freescale SDK. Is it Free (with a capital F) - in other words, it can be >> distributed and redistributed freely by anyone in a way acceptable to the Free >> Software Foundation (FSF)? That means really, is it one of the licenses here: >> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses >> >> If it is one of those licenses, that will probably mean it's okay (unless the >> GPL exception clause in the eCos license causes some conflict). Furthermore, >> we can directly incorporate any files you use directly into the port, avoiding >> any problems with users having to build with an SDK which lives elsewhere. >> >> >>> Before I register, I want to have a strategy in place to deal with >>> Freescale code. Do I replace all the Freescale code line by line until >>> nothing is left, >> Assuming it needs to be replaced... >> >> Replacing it line by line is risky. Copyright is about ideas, not just who >> typed it in. If you use the same, or a sufficiently similar, API or design to >> theirs, it risks infringing the copyright. Not only must it not be the API, it >> must not be able to be considered to have been derived from the API. >> >> In some cases, people have gone to the extent of "clean room" implementations >> to avoid this sort of thing, but I don't think that's likely to be needed. But >> really what's wanted is to effectively do what you would have done if the >> Freescale SDK APIs hadn't been there. For some stuff, it can't really be done >> any other way *anyway*, which is fine. For example, an interrupt controller >> mask macro - there's probably only one particular way to do it. Although if, >> for example, you named the function, and any local variables, exactly the same >> way, that might be a problem. Hopefully replacement isn't relevant though. >> >>> or see if Freescale will assign copyright? >> That would certainly be easiest, however I don't think they're going to want >> to assign copyright for their whole SDK! There can only be one owner of the >> code, and it would mean it was no longer Freescale. So that really won't fly. >> However, I think in this case we can have confidence that Freescale are the >> owners of the code, and have the rights to redistribute; that's something we >> have to be more cautious about with other contributors. >> >> Jifl >> >> -- >> eCosCentric Limited http://www.eCosCentric.com/ The eCos experts >> Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 >> Registered in England and Wales: Reg No 4422071. >> ------["Si fractum non sit, noli id reficere"]------ Opinions==mine