Choice of the API for RTEMS v4.8 as a future partition OS for a newLEON compatible open source hypervisor
helder.silva at edisoft.pt
Fri Jan 30 12:18:51 UTC 2009
We are currently performing a work, inside a ESA program, to facilitate
de qualification of RTEMS (version 4.8.0) against de GSWS "B" assurance
Level. Currently we are not using POSIX API, we are only developing for
the RTEMS Classic API.
Hoping that this information would help, kind regards,
De: rtems-users-bounces at rtems.org [mailto:rtems-users-bounces at rtems.org]
Em nome de Metge Jean-Jacques
Enviada: quinta-feira, 29 de Janeiro de 2009 17:40
Para: rtems-users at rtems.com
Assunto: Choice of the API for RTEMS v4.8 as a future partition OS for a
newLEON compatible open source hypervisor
We are currently starting the porting of RTEMS v4.8 on top of a new LEON
compatible open source hypervisor (XtratuM), which is itself in charge
of ensuring the basic principles of time & space partitioning inherited
from the ARINC653 standard.
This specific "RTEMS v4.8 for XtratuM" version, associated to XtratuM
hypervisor (LEON version) will constitute the core of a future open
source modular software & framework dedicated to space applications, and
more particularly to scientific payloads.
We need to choose the API for this future "RTEMS v4.8 for XtratuM"
version, and we are currently hesitating between the native RTEMS API
(widely used in the space domain) and the POSIX API (less used in the
space domain, but obviously more adapted to the practices of the science
domain, that we are currently targetting with this development).
Could anybody provide general comparative information between RTEMS API
and POSIX API for the v4.8 branch, in terms of :
In a more general way, any feeback on POSIX API of RTEMS v4.8 will be
Thanks a lot for your support.
rtems-users mailing list
rtems-users at rtems.com
More information about the users