From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Harco Kuppens <h.kuppens@domain.hid>
Cc: xenomai@xenomai.org, "hooman >> \"Hooman,
J.\"" <Jozef.Hooman@domain.hid>
Subject: Re: [Xenomai-help] probably error in api document
Date: Mon, 15 Sep 2008 16:16:40 +0200 [thread overview]
Message-ID: <48CE6E48.6030808@domain.hid> (raw)
In-Reply-To: <48CE3096.7040502@domain.hid>
Harco Kuppens wrote:
> Hi,
>
> I noticed in the Xenomai native API that the longer rt_create_intr :
>
> int rt_intr_create
> <http://www.xenomai.org/documentation/trunk/html/api/group__interrupt.html#ga0a9d98556ec838008f408a56e79d304>
> (RT_INTR *intr, const char *name, unsigned irq, rt_isr_t isr, rt_iack_t
> iack, int mode)
>
> says in its documentation :
>
> This service can be called from:
>
> * Kernel module initialization/cleanup code
> * Kernel-based task
> * *User-space task*
>
> I find it strange that it could be called from a user-space task.
> I looked in /usr/xenomai/include/native/intr.h but there it really is
> defined when __KERNEL__ is defined.
>
> So I guess this is an error in the API documention?
No, there is no error: the service is implemented both in user-space and
kernel-space, and if you look at native/intr.h, you will see two
definitions of rt_intr_create: one for kernel-space and one for user-space.
Note however that the interface in user-space is not the same as in
kernel-space, that is because in user-space, you are supposed to call
rt_intr_wait to wait for the next interrupt.
--
Gilles.
next prev parent reply other threads:[~2008-09-15 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 9:53 [Xenomai-help] probably error in api document Harco Kuppens
2008-09-15 14:16 ` Gilles Chanteperdrix [this message]
2008-09-15 15:26 ` Harco Kuppens
2008-09-21 18:28 ` Gilles Chanteperdrix
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=48CE6E48.6030808@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Jozef.Hooman@domain.hid \
--cc=h.kuppens@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.