Re: [Yaffs] YAFFS2 in eCOS ==> the "L" word

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Charles Manning
Date:  
To: yaffs
Old-Topics: Re: [Yaffs] YAFFS2 in eCOS
Subject: Re: [Yaffs] YAFFS2 in eCOS ==> the "L" word
On Sunday 26 October 2008 01:36:26 Emmanuel Blot wrote:
> > Sounds great, thanks! (Or if you have no time to clean it up, I'll be
> > glad to see it anyway.)
>
> Here it is:
> http://moaningmarmot.blogspot.com/2008/10/yaffs2-for-ecos.html



Hello all.

I am very pleased to see an eCos port, but I would like to raise the licensing
issue.

eCos is released under the eCos license which has some similarities to GPL,
but has an important exception, that you may also link in
proprietary "application code".

If I understand correctly, eCOS licensing is covered by:
http://ecos.sourceware.org/license-overview.html, the critical clause being: "
       As a special exception, if other files instantiate templates or use 
macros or inline functions from this file, or you compile this file and link 
it with other works to produce a work based on this file, this file does not 
by itself cause the resulting work to be covered by the GNU General Public 
License. However the source code for this file must still be made available 
in accordance with section (3) of the GNU General Public License.


      This exception does not invalidate any other reasons why a work based on 
this file might be covered by the GNU General Public License.


"

YAFFS GPL licensing does not provide this exception

YAFFS is released under GPL or is available under alternate licensing from
Aleph One.

While you may release an eCos + YAFFS combo under GPL this would require that
you also need to release the entire code base, including the "application
code" under GPL. If you want to keep the "application code" under wraps then
you will likely need to arrange suitable licensing with Aleph One.

If I have misunderstood something, then please help to clarify.


Charles