From: Thomas Lockhart <Thomas.Lockhart@domain.hid>
To: "Łukasz Sacha" <dragilla@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] which skin to use
Date: Sun, 30 Oct 2011 19:38:45 -0700 [thread overview]
Message-ID: <4EAE0A35.6030802@domain.hid> (raw)
In-Reply-To: <CAAeYjMmJ_LKimbvRsR5562MaYvrQGJkSx9jeP2RM3FQvewtg5Q@mail.gmail.com>
On 10/30/2011 03:47 PM, Łukasz Sacha wrote:
> Hi,
> I'm working on a device that will process several input signals (2
> analog, about 4 digital and 1 over serial interface) do some
> calculations and control 4 uarts. It will also write some log data to
> a file on an sd card.
> It will probably be a single process working in an infinite loop,
> regularly, say 50 times per second or more.
> I'm a total beginner as it comes to RT and xenomai. I have some
> experience in wrinting programs in C/C++ for linux.
> Which API should do you think will be good for me to start with?
> Which would be better for the application that I want to write?
I'd use the native API (others may have other advice, and I'd listen to
them if so). If you write your program using regular Linux threads, then
you can just add a few calls to convert the threads you need to be RT in
userland.
At 50Hz you might be able to get by with the regular Linux version,
unless you have very tight lag and jitter requirements. If you are going
for kHz then afaicr Linux will just not be able to schedule your tasks.
You can write your code, do initial testing, then add some #ifdef
XENOMAI lines to guard the extra Xenomai calls.
hth
- Tom
next prev parent reply other threads:[~2011-10-31 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 22:47 [Xenomai-help] which skin to use Łukasz Sacha
2011-10-31 2:38 ` Thomas Lockhart [this message]
2011-10-31 9:56 ` 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=4EAE0A35.6030802@domain.hid \
--to=thomas.lockhart@domain.hid \
--cc=dragilla@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.