From: Jona Ostermann <Jona.Ostermann@janztec.com>
To: Jan Kiszka <jan.kiszka@web.de>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: AW: Directory /proc/xenomai/registry/rtipc/xddp does not exist
Date: Tue, 31 Mar 2020 14:03:07 +0000 [thread overview]
Message-ID: <LEXPR01MB0224A5674739063B3262F5028FC80@LEXPR01MB0224.DEUPRD01.PROD.OUTLOOK.DE> (raw)
In-Reply-To: <4426b307-184f-0422-afe8-2d9d41625608@web.de>
Hello Jan,
thank you, you are correct.
Using the xddp-label demo tool the link is created.
So it is an application error and not a Xenomai configuration error.
Best regards
Jona
-----Ursprüngliche Nachricht-----
Von: Jan Kiszka <jan.kiszka@web.de>
Gesendet: Freitag, 27. März 2020 10:07
An: Jona Ostermann <Jona.Ostermann@janztec.com>; xenomai@xenomai.org
Betreff: Re: Directory /proc/xenomai/registry/rtipc/xddp does not exist
On 26.03.20 11:12, Jona Ostermann via Xenomai wrote:
> Hello,
>
> one of our customers hast he problem that he needs a registry link in the directory /proc/xenomai/registry/rtipc/xddp.
> But the directory does not exist, only /proc/xenomai/registry/ exists.
>
> What could be the problem?
> Is a special kernel configuration required or does a special kernel module need to be loaded?
>
The links show up once xddp is being used. You can check that via smokey's xddp test.
If that is not the case, compare configuration and versions of the reference xenomai-images against your setup and share your findings.
Jan
next prev parent reply other threads:[~2020-03-31 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 10:12 Directory /proc/xenomai/registry/rtipc/xddp does not exist Jona Ostermann
2020-03-27 9:07 ` Jan Kiszka
2020-03-31 14:03 ` Jona Ostermann [this message]
2020-04-01 9:38 ` AW: " Jona Ostermann
2020-04-01 11:48 ` Jan Kiszka
2020-04-01 12:42 ` AW: " Jona Ostermann
2020-04-01 12:58 ` 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=LEXPR01MB0224A5674739063B3262F5028FC80@LEXPR01MB0224.DEUPRD01.PROD.OUTLOOK.DE \
--to=jona.ostermann@janztec.com \
--cc=jan.kiszka@web.de \
--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.