From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Eichenberg, Marius" <Marius.Eichenberg@student.hpi.uni-potsdam.de>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Is there a specification?
Date: Thu, 8 Jan 2015 16:35:19 +0100 [thread overview]
Message-ID: <20150108153519.GC21505@hermes.click-hack.org> (raw)
In-Reply-To: <87BB06E7C07D514A96969FF11282F7954DEB98@MXSTU2012.hpi.uni-potsdam.de>
On Thu, Jan 08, 2015 at 03:13:10PM +0000, Eichenberg, Marius wrote:
> Hey folks,
> we're a team of two students at a university in Germany.
>
> Currently we're trying to evaluate how easy it is to map tasks
> from Autosar (OSEK) to Xenomai. Therefore we're looking for a
> specification of Xenomai. Right now we're dealing with the API,
> but this is acutally a little bulky.
The API documentation is big because it documents several
interfaces, the underlying common interface as well as several skins
implemented on top of this common interface. But implementing a new
interface such as OSEK means implementing a new skin, on top of the
common interface only.
For Xenomai 2.x, this common interface resides in kernel-space and
is documented here:
https://xenomai.org/documentation/xenomai-2.6/html/api/group__nucleus.html
For Xenomai 3.x (which is recommended for starting a new
development), this common interface moved to user-space, is based on
the POSIX interface and is documented here:
https://xenomai.org/documentation/xenomai-3/html/xeno3prm/group__alchemy.html
--
Gilles.
next prev parent reply other threads:[~2015-01-08 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 15:13 [Xenomai] Is there a specification? Eichenberg, Marius
2015-01-08 15:35 ` Gilles Chanteperdrix [this message]
2015-01-08 15:39 ` Gilles Chanteperdrix
2015-01-08 16:02 ` Eichenberg, Marius
2015-01-08 16:10 ` Gilles Chanteperdrix
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=20150108153519.GC21505@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Marius.Eichenberg@student.hpi.uni-potsdam.de \
--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.