Alternative License for Parts of MTD?
Hello,
I work with the real-time operating system RTEMS (http://www.rtems.com). The license of this system is GPL with an exception that allows static linking without restrictions:
http://www.rtems.com/license/LICENSE
This is very similar to the eCos license:
http://ecos.sourceware.org/license-overview.html
RTEMS has currently no framework for flash devices. It would be nice if we can use parts of the MTD system, e.g. the header files and device independent support routines like "drivers/mtd/nand/nand_base.c". Is it possible to release parts of the MTD code under the RTEMS or eCos license, or would you categorically refuse this?
Have a nice day!
Signature · 9 lines
Sebastian Huber, embedded brains GmbH Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany Phone : +49 89 18 90 80 79-6 Fax : +49 89 18 90 80 79-9 E-Mail : [email protected] PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
Am 13.04.2012 16:15, schrieb Sebastian Huber:
Quoted 6 lines
Hello,
I work with the real-time operating system RTEMS (http://www.rtems.com).
The license of this system is GPL with an exception that allows static linking without restrictions:
Quoted 6 lines
http://www.rtems.com/license/LICENSE
This is very similar to the eCos license:
I'd contact a lawyer.
Anyway, your GPL-with-an-exception license looks more like LGPL...
Thanks,
//richard
Signature · 6 lines
Phone: +49 7556 91 98 91; Fax.: +49 7556 91 98 86 Firmensitz: 88690 Uhldingen, Auf dem Berg 3 Registergericht: Amtsgericht Freiburg i. Br., HRB 700 806; StNr. 87007/07777; Ust-Id Nr.: DE252739476 Geschäftsführer: Heinz Egger, Thomas Gleixner
Hello Richard,
thanks for the feedback.
Quoted 9 lines · Richard Weinberger
Am 13.04.2012 16:15, schrieb Sebastian Huber:
Quoted 8 lines
Hello,
I work with the real-time operating system RTEMS (http://www.rtems.com).
The license of this system is GPL with an exception that allows static linking without restrictions:
Quoted 7 lines
Quoted 4 lines
This is very similar to the eCos license:
I'd contact a lawyer.
Anyway, your GPL-with-an-exception license looks more like LGPL...
Please have a look at:
http://sources.redhat.com/ml/ecos-discuss/2002-05/msg00206.html
Signature · 9 lines
Sebastian Huber, embedded brains GmbH Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany Phone : +49 89 18 90 80 79-6 Fax : +49 89 18 90 80 79-9 E-Mail : [email protected] PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
Quoted 10 lines · Sebastian Huber
Hello,
I work with the real-time operating system RTEMS (http://www.rtems.com). The license of this system is GPL with an exception that allows static linking without restrictions:
http://www.rtems.com/license/LICENSE
This is very similar to the eCos license:
Quoted 7 lines
http://ecos.sourceware.org/license-overview.html
RTEMS has currently no framework for flash devices. It would be nice if we can use parts of the MTD system, e.g. the header files and device independent support routines like "
drivers/mtd/nand/nand_base.c". Is it possible to release parts of the MTD code under the RTEMS or eCos license, or would you categorically refuse this?
Irrespectively of what random people in the mailing list think, this is a question to layers. And I guess you'd need to have permission of all copyright holders, which I guess all people who contributed, and this is practically impossible to do. But I do not know for sure whether this is correct or not :-)
Signature · 2 lines
Best Regards, Artem Bityutskiy
Artem, et al.:
Quoted 5 lines
Irrespectively of what random people in the mailing list think, this is a question to layers. And I guess you'd need to have permission of all copyright holders, which I guess all people who contributed, and this is practically impossible to do. But I do not know for sure whether this is correct or not :-)
Yes, the current opinion seems to be that to change the licensing terms for a given module from restrictive terms (such as (L)GPL) to less-restrictive terms, one needs the assent of anyone who ever contributed to that module. That's why conversion to a more-restrictive license such as (l)GPL tends to be a "sticky" (one-way) conversion.
The best alternative is to re-write the functionality in a "clean room" environment and then release it under your choice of license terms. One can certainly emulate the design of the existing code without violating any copyright. Patents are, of course, another (and separate) issue; the existing design may incorporate patented methods which one can't necessarily emulate freely.
Atlant
(IANAL, etc.)-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Artem Bityutskiy
Sent: Friday, April 13, 2012 11:29
To: Sebastian Huber
Cc: Linux MTD
Subject: Re: Alternative License for Parts of MTD?
Quoted 10 lines · Sebastian Huber
Hello,
I work with the real-time operating system RTEMS (http://www.rtems.com). The license of this system is GPL with an exception that allows static linking without restrictions:
http://www.rtems.com/license/LICENSE
This is very similar to the eCos license:
Quoted 7 lines
http://ecos.sourceware.org/license-overview.html
RTEMS has currently no framework for flash devices. It would be nice if we can use parts of the MTD system, e.g. the header files and device independent support routines like "
drivers/mtd/nand/nand_base.c". Is it possible to release parts of the MTD code under the RTEMS or eCos license, or would you categorically refuse this?
Irrespectively of what random people in the mailing list think, this is a question to layers. And I guess you'd need to have permission of all copyright holders, which I guess all people who contributed, and this is practically impossible to do. But I do not know for sure whether this is correct or not :-)
--
Best Regards,
Artem Bityutskiy
This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.
Thank you.
Please consider the environment before printing this email.