From: Jan Kiszka <jan.kiszka@domain.hid>
To: Alessio Igor Bogani <abogani@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Three questions about RTDM
Date: Thu, 02 Feb 2006 10:28:54 +0100 [thread overview]
Message-ID: <43E1D0D6.2020003@domain.hid> (raw)
In-Reply-To: <1138870064.8753.19.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
Alessio Igor Bogani wrote:
> Hi all, Hi Jan,
>
> I apologize for my (very) bad english.
>
> I have three simple questions about RTDM:
>
> 1) Where may I find a more detailed documentation about RTDM?
More detailed than what? Have you already discovered the online docs on
www.xenomai.org?
>
> 2) Now I'm attempting to write a simple device driver with RTDM: Can
> someone show me a standard GNUMakefile/Makefile to compile it?
Take a look at the heartbeat example on
www.rts.uni-hannover.de/mitarbeiter/kiszka/rtaddon
This works for 2.6 kernels and Xenomai 2.0.x. I still need to update it
for Xenomai 2.1, where compilation melts down to simple out-of-tree
kernel module generation. Does anyone else here have a generic Makefile
for all kernel and Xenomai versions at hand?
>
> 3) Device driver written with RTDM must be released under GPL?
> Or, as like Xenomai, the developer is free to choose the license that
> prefer for his/her sw based on it?
>
For me, an RTDM driver using the official RTDM API would be no derived
work, thus would not necessarily have to be GPL. But I cannot speak for
all other developers involved in the APIs you may have to use in your
driver (moreover, RTDM is also not only my own work). Actually, this
does not solely depend on RTDM, this is a linux kernel issue as you put
your module inside this GPL'ed system. As long as there are no urging
needs (non-extractable IP inside the driver core that must be kept
closed), I would recommend no one theses days to develop binary-only
kernel modules anymore (this is also one reason why you shouldn't write
closed-source RT kernel application modules, BTW).
If you just prefer another open source license, release your driver
under both GPL and that other license. But if you plan to keep it
closed, I can only recommend to ask a lawyer about legal pros and cons
of this approach.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-02-02 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 8:47 [Xenomai-help] Three questions about RTDM Alessio Igor Bogani
2006-02-02 9:28 ` Jan Kiszka [this message]
2006-02-02 10:35 ` Alessio Igor Bogani
2006-02-02 10:43 ` Jan Kiszka
2006-02-02 15:27 ` Alessio Igor Bogani
2006-02-02 16:10 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E1D0D6.2020003@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=abogani@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.