From: Philippe Gerum <rpm@xenomai.org>
To: xenomai@xenomai.org
Subject: [CXP][RFC] pick POSIX/cobalt for the common user API
Date: Sun, 06 Dec 2020 11:46:25 +0100 [thread overview]
Message-ID: <87mtyr1abi.fsf@xenomai.org> (raw)
The common Xenomai platform specification is about defining the
commonalities among future Xenomai releases starting from 3.3, including
the Xenomai 4 series based on a next generation (EVL) core. A common API
available to applications for issuing requests to the real-time core is
part of this specification.
Implementing such interface would not preclude other APIs from
co-existing in particular releases. However, use of this common API
only would guarantee portability across releases.
Excluding the legacy RTOS emulators such as VxWorks and pSOS, Xenomai
3.x provides two main APIs, a POSIX-compliant one (libcobalt) and a
custom RTOS API aka Alchemy (libalchemy) on top of the Copperplate
interface.
PROPOSAL: Pick libcobalt as the common API defined by the CXP.
As a consequence, Xenomai 4 would provide two direct interfaces to the
underlying EVL core: via the libevl API [1] which is readily
available, and its own implementation of libcobalt as part of a CXP
compliance.
applications
....................................
libalchemy libevl libcobalt
| | |
| | |
libcopperplate | |
| | |
| | |
libcobalt | |
| | |
v v v
(Cobalt core) (EVL core)
----------- ---------
Xenomai 3.x Xenomai 4
Thanks,
[1] https://evlproject.org/core/user-api/
--
Philippe.
next reply other threads:[~2020-12-06 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 10:46 Philippe Gerum [this message]
2020-12-07 2:16 ` [CXP][RFC] pick POSIX/cobalt for the common user API chensong
2020-12-07 10:12 ` Philippe Gerum
2020-12-08 1:22 ` chensong
2020-12-07 13:58 ` Wolfgang Denk
2020-12-11 6:12 ` chensong
[not found] ` <5fcd902b.1c69fb81.79300.444fSMTPIN_ADDED_BROKEN@mx.google.com>
2020-12-07 6:59 ` Greg Gallagher
2020-12-07 8:09 ` chensong
2020-12-14 7:22 ` Wolfgang Denk
2020-12-14 12:44 ` Jan Kiszka
2020-12-14 16:00 ` Greg Gallagher
2021-01-03 17:05 ` Philippe Gerum
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=87mtyr1abi.fsf@xenomai.org \
--to=rpm@xenomai.org \
--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.