From: Jan Kiszka <jan.kiszka@domain.hid>
To: Carsten Emde <Carsten.Emde@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>, ag-automation@domain.hid
Subject: Re: [Xenomai-core] [ag-automation] [ANNOUNCE] RTDM for Linux-rt
Date: Fri, 13 Apr 2007 07:48:10 +0200 [thread overview]
Message-ID: <461F199A.5070803@domain.hid> (raw)
In-Reply-To: <461EBF65.5010604@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]
Hi Carsten,
[adding xenomai to cc again]
Carsten Emde wrote:
> Wolfgang,
>
>> Attached you can find a README on how to install and use RTDM-native and
>> the current implementation status.
> I couldn't stop my curiosity to see it working. So, I downloaded the
> material from the repository and attacked linux-2.6.21-rc6-rt0 after
> enabling everything available in the "Real-time subsystem". BTW:
> Wouldn't it be less confusing to call this section differently? For
> example "RTDM subsystem" or similar? Sorry, just a first thought - there
> is so much real-time everywhere.
Yes, I think so as well. The menu naming comes from the history of the
build system (Xenomai).
>
> I then tried to build a new kernel. With a single exception, everything
> compiled without warning. The exception was switchtest that refused to
> build:
>
> drivers/xenomai/testing/switchtest.c:1:27: error: nucleus/synch.h: No
> such file or directory
> drivers/xenomai/testing/switchtest.c:2:28: error: nucleus/thread.h: No
> such file or directory
> drivers/xenomai/testing/switchtest.c:5:32: error: asm/xenomai/fptest.h:
> No such file or directory
That driver shouldn't be part of rtdm-native, it's for stress-testing
the Xenomai nucleus.
>
> After disabling it, all sources could be compiled without any further
> problem. Linking xeno_rtdmtest.ko and xeno_16550A.ko, however, failed:
> WARNING: "hrtimer_init_sleeper"
> [drivers/xenomai/testing/xeno_rtdmtest.ko] undefined!
> WARNING: "hrtimer_init_sleeper" [drivers/xenomai/serial/xeno_16550A.ko]
> undefined!
At least in 2.6.20, hrtimer_init_sleeper() is not exported to modules.
Hmm, maybe Wolfgang tested both as built-in components, but that would
just be a workaround.
>
> I then disabled these two modules as well. The rest could be compiled
> and linked smoothly. The kernel was able to boot and the modules
> xeno_irqbench and xeno_can_virt could be loaded normally.
>
> I then tried linux-2.6.20-rt8 - same situation as described above.
>
> Will do some testing later. Anybody out there who would like to join the
> RTDM-Native Testing Group?
Would love to, but short on time...
You may want to start by playing with irqbench [1] (IRQ latency tests
across nullmodem or laplink cable) or with the CAN stack, for which
xeno_can_virt offers you a virtual local bus of two CAN interfaces [2].
Jan
[1]http://www.rts.uni-hannover.de/xenomai/lxr/source/doc/txt/irqbench.txt
[2]http://www.rts.uni-hannover.de/xenomai/lxr/source/src/utils/can/README
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2007-04-13 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 11:09 [Xenomai-core] [ANNOUNCE] RTDM for Linux-rt Wolfgang Grandegger
[not found] ` <461EBF65.5010604@domain.hid>
2007-04-13 5:48 ` Jan Kiszka [this message]
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=461F199A.5070803@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Carsten.Emde@domain.hid \
--cc=ag-automation@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.