From: Philippe Gerum <rpm@xenomai.org>
To: ckreider <ckreider@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] inscrutable pipes
Date: Thu, 14 Sep 2006 18:17:57 +0200 [thread overview]
Message-ID: <1158250677.5040.199.camel@domain.hid> (raw)
In-Reply-To: <3BDC517D-07A0-4BD3-9C6A-332E76B32615@domain.hid>
On Thu, 2006-09-14 at 12:06 -0400, ckreider wrote:
> Proud though I am, it is time to ask for help. I have used pipes with
> RTLinux but want to use Xenomai this time. I can't get pipes working.
>
>
> (as an aside, I saw on here where if you do make install, it will
> create the necessary /dev/rtp* entries. I work on a development host
> and do not compile on the target, so I do not run make install. I
> finally found the mknod magic in a message on this list)
>
>
> I am using Xenomai 2.2.1 with a 2.6.17.8 kernel.
>
The message pipe support has been refactored recently to behave like
classic FIFOs when accessed through the /dev/rtp* interface. All changes
have been committed to our repos, and should be obtained from there
until we roll out v2.2.3.
You can get the code through SVN at this URL:
http://svn.gna.org/viewcvs/xenomai/branches/v2.2.x/
Could you try it, and let us know if it solves the issue you raised?
TIA,
--
Philippe.
next prev parent reply other threads:[~2006-09-14 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 16:06 [Xenomai-help] inscrutable pipes ckreider
2006-09-14 16:17 ` Gilles Chanteperdrix
[not found] ` <1BECC866-4567-477D-9A18-144496828EB7@domain.hid>
2006-09-14 21:22 ` Gilles Chanteperdrix
2006-09-23 17:59 ` Gilles Chanteperdrix
2006-09-14 16:17 ` Philippe Gerum [this message]
[not found] ` <38A01364-EC56-46D9-9768-A14979EA98E5@domain.hid>
[not found] ` <1158326750.5072.2.camel@domain.hid>
2006-09-16 11:32 ` ckreider
2006-09-17 12:05 ` Jan Kiszka
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=1158250677.5040.199.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=ckreider@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.