This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: YAFFS2 software license and eCOS software license compatiable?
- From: Andrew Lunn <andrew at lunn dot ch>
- To: J?rgen Lambrecht <J dot Lambrecht at televic dot com>
- Cc: "ecos-discuss at ecos dot sourceware dot org" <ecos-discuss at ecos dot sourceware dot org>, Tim michals <tcmichals at yahoo dot com>, Rutger Hofman <rutger at cs dot vu dot nl>
- Date: Sat, 25 Oct 2008 11:47:56 +0200
- Subject: Re: [ECOS] YAFFS2 software license and eCOS software license compatiable?
- References: <860331.44618.qm@web53206.mail.re2.yahoo.com> <20081023143244.GB24016@lunn.ch> <4901DE68.1030708@televic.com>
> Indeed. We will probably pay for YAFFS.
> But is it not possible to put the YAFFS "interface code" into ecos? :
> - HW interface code in /devs/flash/nand and /devs/flash/[arm]/[eb9260]
> - file system "interface" functions
> a sort of yaffs_ecos.c , just like fs/jffs2/../fs-ecos.c
With care, this can be done. You have to not use any YAFFS code when
writing such interface code. If you derive the eCos code from YAFFS
code, or any other plain GPL code, the plain GPL license has to be
used.
If you write this could by only looking at the YAFFS documentation and
not using any GPL code, the new work is then not a derivative of YAFFS
or some other GPL work, and so you can put the eCos modGPL license on
it.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss