All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Levesque <vleves@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Writing from user space direct to IO	Ports	without mode switches
Date: Fri, 20 Jul 2007 15:28:41 -0400	[thread overview]
Message-ID: <46A10CE9.7090603@domain.hid> (raw)
In-Reply-To: <46A06886.5000703@domain.hid>

Hi Jan,
> Hope that helped to clarify the situation. Now please let us know which
> sentence(s) from the doc may have misled your understanding of the mode
> switching feature. Maybe we have to rephrase them.
>   
I wasn't referring to any part of the docs in particular. If I remember 
correctly, I came across rt_task_set_mode(...) in the API documentation 
and naively assumed that a task could be set to secondary mode when it 
is expected to frequently trigger mode switches (e.g. data logging, 
graphical user interface). Perhaps a short note could be added to the 
function's description to the affect that the T_PRIMARY bit should be 
modified manually only in exceptional cases. Or maybe I'm the only one 
who got confused!

In any case, thank you for these clarifications!

Vincent Levesque
vleves@domain.hid




      reply	other threads:[~2007-07-20 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 22:23 [Xenomai-help] Writing from user space direct to IO Ports without mode switches Renner Johannes
2007-07-18  6:47 ` Gilles Chanteperdrix
2007-07-18 10:19   ` [Xenomai-help] Writing from user space direct to IO Ports withoutmode switches Renner Johannes
2007-07-18  8:22 ` [Xenomai-help] Writing from user space direct to IO Ports without mode switches Philippe Gerum
2007-07-18 10:12   ` Renner Johannes
2007-07-18 10:47     ` Philippe Gerum
2007-07-19 21:10       ` Vincent Levesque
2007-07-20  7:47         ` Jan Kiszka
2007-07-20 19:28           ` Vincent Levesque [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=46A10CE9.7090603@domain.hid \
    --to=vleves@domain.hid \
    --cc=jan.kiszka@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.