Schlägl Manfred jun. wrote: > Its a very difficult question. I'm also interestet in it. > > Adeos is under GPL. > Xenomai-code in ksrc is under GPL; > userspace Xenomai-code is under LGPL > > Kernel-sources are under GPL, because several functions of the kernel can > only be used by GPL-licensed modules.
Additionally, it is The Right Thing that when you modify such common infrastructure like the Xenomai core, you should be urged to provide the same freedom to users of your modifications. This can best be reached by contributing them back to mainstream. > Userspace code is under LGPL, but the kernel-code is used by syscalls ... > > So it's really hard to determine if applications have to be GPLed or LGPLed > at this point... > > > BUT! > > The header-files are GPLed with following exception: > > COPYING: > ... > As a special exception to the following license, the Xenomai > project gives permission for additional uses of the header files > contained in this directory. > > The exception is that, if you include these header files unmodified to > produce application programs executing in user-space that use > Xenomai services by normal Xenomai system calls, this does not > by itself cause the resulting executable to be covered by the GNU > General Public License. This is merely considered normal use of the > Xenomai system, and does not fall under the heading of "derived > work". > > This exception does not however invalidate any other reasons why the > executable file might be covered by the GNU General Public License. In > any case, this exception never applies when the application code is > built as a static or dynamically loadable portion of the Linux kernel. > > This exception applies only to the code released by the Xenomai > project under the name Xenomai and bearing this exception notice. > If you copy code from other sources into a copy of Xenomai, the > exception does not apply to the code that you add in this way. > ... > > > But is this exception airtight? Is it hard enought to stand a court-case? I > don't know. > Legal question are always tricky. My believe as a non-lawyer is that Xenomai's license terms are fairly clear in that they allow user-space development _against_ libs/headers/syscalls under any license. Working _inside_ the user libs or even the Xenomai core is of course governed by LGPL and GPL, respectively. Writing non-GPL kernel space applications or drivers is a far trickier question. Any such "program" is never only a Xenomai user, it's first of all a kernel module. And the "trend" in the kernel community clearly goes towards GPL-only. Some developers (i.e. copyright holders) already consider ANY non-GPL module an infringement today. Xenomai cannot (and doesn't want to) put any escape-door against this legitimate decision. Xenomai is just an (out-of-tree) subsystem of Linux. Regarding RTDM drivers: My believe is that any potential non-GPL driver publisher should better consult a layer. I would rather try (harder) to partition the system in a way that relevant intellectual properties are always in hardware/firmware or user-space. In the end this makes life easier - and saves us from seeing more and more lawyers hanging around ;). The roadmap of RTDM contains one topic that aims at helping driver developers here (user-space driver API), but it's an extension not yet backed up with concrete resources. Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
