From: Steven Seeger <steve@domain.hid>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@domain.hid>,
Jan Kiszka <jan.kiszka@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] no-brainer issue found, but not solved
Date: Wed, 22 Feb 2006 06:21:50 -0800 [thread overview]
Message-ID: <C021B37E.24C4%steve@domain.hid> (raw)
In-Reply-To: <fd6a47a90602211320k21eb3b8w@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
There is a awful amount of code in this project, and I should point out that
this same code did not exhibit these problems under a fusion cvs from
October. I can see about posting the full code, but my supervisors don¹t
want anything having our hardware addresses in it going out.
This is an x86 board, so inb/outb are just instructions.
I know about the volatile thing but that isn¹t my problem. I¹m having
realtime preemption issues.
Steven
On 2/21/06 1:20 PM, "Jeroen Van den Keybus" <jeroen.vandenkeybus@domain.hid>
wrote:
> It would be helpful if a complete code could be posted. That means, including
> the main() function, in which the task dispatching is done as well.
>
> Furthermore, be sure to declare counting variables inside waiting loops with
> the 'volatile' specifier. The compiler might optimize it away otherwise.
>
> Another, maybe dumb suggestion: how is inb() / outb() actually implemented on
> your platform ?
>
>
> Jeroen.
>
>
[-- Attachment #2: Type: text/html, Size: 1513 bytes --]
next prev parent reply other threads:[~2006-02-22 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 17:38 [Xenomai-help] no-brainer issue found, but not solved Steven Seeger
2006-02-21 17:57 ` Jan Kiszka
2006-02-21 18:15 ` Steven Seeger
2006-02-21 18:36 ` Jan Kiszka
2006-02-21 21:20 ` Jeroen Van den Keybus
2006-02-22 14:21 ` Steven Seeger [this message]
2006-02-22 15:00 ` Jan Kiszka
2006-02-24 9:01 ` Philippe Gerum
2006-02-24 14:00 ` Steven Seeger
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=C021B37E.24C4%steve@domain.hid \
--to=steve@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=jeroen.vandenkeybus@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.