RFC : Heap management using TLSF

[Pavel Pisa]

On Thursday 31 July 2008 06:10:28 pm Joel Sherrill wrote:
> So you really are up to the license being a problem.

Hello everybody,

I am forwarding Ismael's reply to the list, because his direct reply
is on hold for moderator or discarded by the list rules.
The TLFS licensing has been already adjusted to be compatible
with RTEMS after Tim's yesterday inquiry. So there should
not be problem to use code in RTEMS core.

There is exact wording of the exception

As a special exception, including TLSF header files in a file, or linking with
other files objects to produce an executable application, is merely considered
normal use of the library, and does *not* fall under the heading of "derived
work". Therefore does not by itself cause the resulting executable application
to be covered by the GNU General Public License. This exception does not
however invalidate any other reasons why the executable file might be covered
by the GNU Public License.

Best wishes,

                     Pavel

----------  Forwarded Message  ----------

Subject: Re: RFC : Heap management using TLSF
Date: Thursday 31 July 2008
From: Ismael Ripoll <iripoll at disca.upv.es>
To: Pavel Pisa <ppisa4lists at pikron.com>

Helo Pavel,

 Yesterday, we received a mail from Tim, asking to adapt the TLSF
license to the RTEMS one. We agreed on that since the RTEMS is line the
Linux kernel and also like the LGPL (I see no diferences at all).

 In any case, I think that it is better to state explicitly the limits
of the GPL (what is considered "derived work").

  A new version of the TLSF has been released (2.4.3) prepared to be
used with RTEMS, this new version includes minor syntactical changes to
compile it on a non-gcc compiler.

http://rtportal.upv.es/rtmalloc/node/8

See the COPYING file. It includes an explicit GPL exception, similar to
RTEMS one.

We are open to perform other "legal" claims to make sure that TLSF can
freely be used in RTEMS.

Regards,
Ismael.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.rtems.org/pipermail/users/attachments/20080801/70cae9c8/attachment-0001.bin>