From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Robert Gubler <rgubler@domain.hid>
Cc: Xenomai-help@domain.hid, Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] [RTnet-users] RTNet in non-TDMA mode?
Date: Sat, 27 Oct 2007 21:04:55 +0200 [thread overview]
Message-ID: <47238BD7.1040501@domain.hid> (raw)
In-Reply-To: <e4ef24880710271153qb9c0b27y937f3d87e16f0922@domain.hid>
Hi Rob,
Thanks for this response.
> But my question remains -purely out of interest- why non-rt devices and
> rt devices can _fundamentally_ not share an IRQ?
>
>
>
> My understanding is adeos-ipipe/xenomai provide an interrupt abstraction
> layer underneath Linux. If there is more than one consumer of an
> interrupt it has to be copied/forwarded to all those that need it. If
> an IRQ is shared with an RT application, and the Linux kernel I would
> imagine this would create some level of indeterministic RT software.
IRQs are incoming (to the kernel/CPU) signals IIUC. I imagine that at
the end of these incoming IRQ's sit ISRs just waiting for IRQ and ready
to respond to it in whatever manner they usually do. If this
understanding is correct (which it probably is not) then I would not be
able to conceive of a reason why the IRQ could not be passed on to the
NON RT interrupt service routine after it has been handled by the
RT-ISR. But I reiterate that my understanding of these things is as
sketchy as my interest to improve the sketchiness is big. :)
> This is probably a good question for the xenomai, or adeos-ipipe mailing
> list.
Have already done so earlier. I was not aware initially that this thread
was on the RTnet list. The duplicate and capitalised RTNet in the
subject must have been mysteriously obscured by my client for a while. :)
Roland
>
> -Rob
next prev parent reply other threads:[~2007-10-27 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e4ef24880710261838l4d1961a5s8117d116be499cee@domain.hid>
[not found] ` <e4ef24880710262040r718b58f7xa2e5f89156d9024b@domain.hid>
[not found] ` <e4ef24880710262126g658f3f7ci534ca13df32b2e0e@domain.hid>
[not found] ` <4723118D.9060807@domain.hid>
[not found] ` <472326E6.9080103@domain.hid>
[not found] ` <47232A0C.60705@domain.hid>
2007-10-27 13:43 ` [Xenomai-help] [RTnet-users] RTNet in non-TDMA mode? Roland Tollenaar
2007-10-27 18:53 ` Robert Gubler
2007-10-27 19:04 ` Roland Tollenaar [this message]
2007-10-27 19:17 ` Robert Gubler
2007-10-27 19:52 ` Roland Tollenaar
2007-10-28 10:53 ` Jan Kiszka
2007-10-28 10:59 ` 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=47238BD7.1040501@domain.hid \
--to=rwatollenaar@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=rgubler@domain.hid \
--cc=rolandtollenaar@domain.hid \
/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.