All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Schwab <schwab@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Porting / API Questions
Date: Thu, 7 Sep 2006 11:12:28 +0200	[thread overview]
Message-ID: <200609071112.28817.schwab@domain.hid> (raw)
In-Reply-To: <44FF3C26.10501@domain.hid>

On Wednesday 06 September 2006 23:22, Jeff Webb wrote:
> I am attempting to port a real-time simulation from rtlinux3.2-pre3 (GPL)
> to xenomai.  The application consists of a kernel module, and a user-space
> application.  I would like to port the application to xenomai with as few
> changes as possible, and then make improvements in incremental steps.  I am
> currently working on a Fedora Core I, Linux-2.4.32 / xenomai-2.1-rc4
> system.
Why not the latest version of xenomai (2.2) ? 
>
> In this simulation, we use the rtlinux POSIX-like API for threads, timing,
> and writing-to / reading-from real-time FIFOs.  It looks like the
> xeno_posix API will allow me to port the thread and timing code with very
> few (if any) changes.  There does not appear to be a kernel-space version
> of read and write for use on xenomai pipes.  Am I missing something?
When I did the same switch (9 month ago now) I choose to combine
the kernel / user space split in one application and switched to the native 
API at the same time.
I think it was a good decision, since now the application is independent of 
the exact kernel version and is easier to debug.
Only the driver for the analog and digital I/O is still a kernel module (RTDM)

The RT kernel threads of the original version are now threads of the user 
space app running in primary mode. This means the split between RT/non-RT
is basically the same as before, but now they all run in user space.

>
> I noticed that the rtai API appears to support real-time FIFOs, much like
> the old RTLinux API.  In light of this discovery, I changed my RT-Linux
> code to use rtf_get and rtf_put calls (instead of read/write).  This code
> seems to compile for xeno_rtai without too much trouble.
>
> Is it okay to use the POSIX API for threads and timing, and the rtai API
> for FIFOs?  It seems like this is working, but I want to make sure that
> there are no hidden problems.
>
> I have compiled my application for xenomai.  The kernel module loads fine,
> and the userspace application runs as well.  The problem I am having now is
> creating a large FIFO, which is why I wrote the previous email.
Why do You need a FIFO this large ?
Why not using shared memory for the data, and the FIFO for passing
signals/commands ?

Ulrich
>
> Any input on this porting project would be appreciated.  Thanks!
>
> -Jeff
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


  reply	other threads:[~2006-09-07  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 21:22 [Xenomai-help] Porting / API Questions Jeff Webb
2006-09-07  9:12 ` Ulrich Schwab [this message]
2006-09-07 20:15   ` Jeff Webb
2006-09-07 10:35 ` Jan Kiszka
2006-09-07 19:56   ` Jeff Webb
2006-09-08 11:06     ` Gilles Chanteperdrix
2006-09-07 11:07 ` Gilles Chanteperdrix
2006-09-07 20:03   ` Jeff Webb
2006-09-08 15:12     ` 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=200609071112.28817.schwab@domain.hid \
    --to=schwab@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.