All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Remi Lefevre <rlefevre@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Some beginner technical questions
Date: Sat, 26 Jan 2008 16:33:35 +0100	[thread overview]
Message-ID: <479B52CF.6010306@domain.hid> (raw)
In-Reply-To: <4e0b9cb00801240505y77d71956w994e312be382f91b@domain.hid>

Remi Lefevre wrote:
> 
> I saw on some introduction slides that an arinc 653 skin would be possible.
> Emulating the arinc 653 is certainly possible, but if a real arinc 653
> system is considered, this raises a few technical issues.

Issues related to software certification for use in mission critical
contexts such as avionics are well beyond the sole Adeos/Xenomai layer;
firstly, we depend on Linux which would represent quite a job to
certify, not to speak of the toolchains used to build the software which
would need to be certified as well.

Therefore, it seems more reasonable to consider Arinc653 over Xenomai
for emulation duties, i.e. allow developers to implement (most of) their
applications over the APEX in a cosy Linux environment, before banging
anyone's head on the real target is ever needed. What Xenomai could
bring in the picture is accurate emulation, regarding both the APEX
behaviour and timeliness.

In that respect, what should be said about Xenomai regarding Arinc653 is
that the building blocks provided by the former would be enough to
properly emulate the latter (including temporal partitioning).

-- 
Philippe.


      parent reply	other threads:[~2008-01-26 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 13:05 [Xenomai-core] Some beginner technical questions Remi Lefevre
2008-01-25 19:30 ` Jan Kiszka
2008-01-25 20:01   ` Gilles Chanteperdrix
2008-01-26 15:33 ` Philippe Gerum [this message]

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=479B52CF.6010306@domain.hid \
    --to=rpm@xenomai.org \
    --cc=rlefevre@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.