From: Jan Kiszka <jan.kiszka@domain.hid>
To: rolandtollenaar@domain.hid
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] [RTnet-users] RTNet in non-TDMA mode?
Date: Sun, 28 Oct 2007 11:59:37 +0100 [thread overview]
Message-ID: <47246B99.2090307@domain.hid> (raw)
In-Reply-To: <47234083.4000602@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
Roland Tollenaar wrote:
>>> between RTdevices and non-RT devices crash the system? And whether I
>>> understand correctly that later versions (2.4 up?) of xenomai do not
>>> have the problem of the freezing system at least.?
>> Since Xenomai 2.3, actually, no system is supposed to "crash" anymore
>> when IRQ conflicts between the domains arise. But if you loose, e.g.,
>> your USB keyboard or your serial console or whatever input device due to
>> a conflict, you may get the impression of a crash. However, if anyone
>> suspects that something else happens on his system, please report the
>> findings to the Xenomai mailing list!
>
> The systems I have found to "crash" all used PS/2 input device and
> normal VGA monitor. Generally a freeze is initiated by some grafical
> action in X after starting rtnet. dmesg will tell me that there is a
If there is a conflict with your graphic adapter, using a VESA X driver
or disabling acceleration (Option "NoAccel") should remove the need to
use the related IRQ under Linux.
> shared IRQ, and in some cases it will disable it. In the latter case the
> system does not freeze but I still have to find another IRQ address.
> When there is a shared interrupt then there might be a freeze. If it
> does not freeze immediately it never freezes and the shared IRQ is no
> problem. For a while I thought there was only a problem with the VGA
> device and the rtnet card so if I kept those two off the same IRQ there
> would be no problem. On other machines this theory was brutally smashed.
> Sorry I cannot be more specific here since all problems in the end are
> "solved".
>
> Hmm, I am just considering that since I use live linux it may be that
> the conflict was between the rtnet card and a USBport that gives access
> to the usbstick(s).
>
> But my question remains -purely out of interest- why non-rt devices and
> rt devices can _fundamentally_ not share an IRQ?
>
> kind
>
> regards,
>
> Roland.
>
>
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-10-28 10:59 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
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 [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=47246B99.2090307@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-help@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.