All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Michel He <michel.he@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] netrpc
Date: Wed, 31 Mar 2010 15:33:46 +0200	[thread overview]
Message-ID: <4BB34F3A.3060105@domain.hid> (raw)
In-Reply-To: <20100331143432.44386sa8ez2p2q2o@domain.hid>

Michel He wrote:
> Hello all,
> 
>     I'm currently trying to port xrtai-lab to xenomai, inside of it  
> there's the netrpc interface used to make communication between tasks.  
> However, there is no equivalent for Xenomai, which makes the port  
> quite impossible !

Nothing is impossible. :)

> So is there any chance to fulfill that, and with/or  
> without RTNet ? To do that, it should have something to do with socket  
> programming. Any experience encountered it is welcomed.

Well, you could start with mapping the existing RTAI API calls in
xrtai-lab on local Native calls. That will already give you a
non-distributed port.

But there is also no magic behind netrpc. It just uses RTnet for remote
calls, and that works for Xenomai at least equally well. You could
simply write a RPC API extension for libnative (a pure user space job).
That lib would do the routing, encapsulate and forward non-local calls
to some sockets provided via the RTDM API.

BTW, the same should be feasible for a POSIX-based API extension, which
would have the advantage of making the result easier portable to plain
Linux.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2010-03-31 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 12:34 [Xenomai-help] netrpc Michel He
2010-03-31 13:33 ` Jan Kiszka [this message]
2010-04-13  8:13   ` Michel He
2010-04-13 23:59     ` Jan Kiszka
2010-04-15 14:45   ` Michel He
2010-04-15 15:03     ` 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=4BB34F3A.3060105@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=michel.he@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.