From: Johann Obermayr <johann.obermayr@sigmatek.at>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] rtdm_event_pulse in user space
Date: Tue, 26 Nov 2013 12:06:45 +0100 [thread overview]
Message-ID: <529480C5.7040901@sigmatek.at> (raw)
In-Reply-To: <52947E3E.7060304@xenomai.org>
Am 26.11.2013 11:55, schrieb Philippe Gerum:
> On 11/26/2013 11:50 AM, Johann Obermayr wrote:
>> Am 25.11.2013 10:46, schrieb Philippe Gerum:
>>> On 11/25/2013 10:39 AM, Johann Obermayr wrote:
>>>> Hello,
>>>>
>>>> Is there a way to make a
>>>> rt_event_pulse.
>>>> A kernel function rtdm_event_pulse is available, but no user space
>>>> function.
>>>>
>>>
>>> rtdm_event_pulse() is part of the inter-driver API, which explains why
>>> there is no userland access to it. Assuming you need to wake up a RTDM
>>> task waiting on a particular event via rtdm_event_wait(), then you
>>> have to implement an rt/nrt ioctl handler in your RTDM driver which
>>> will send the event. Userland can issue this ioctl request from
>>> userland.
>>>
>> Hi,
>>
>> in userspace there are rt_event_signal & rt_event_clear, but no
>> rt_event_pulse.
>> i need rt_event_pulse to make my source compatible with EventPulse
>> Window-Function.
>>
>>
>
> You mentioned both rt_event_pulse, and rtdm_event_pulse in your
> initial post, which is confusing: those are two different APIs.
>
> RT_EVENTs - posted by rt_event_signal - from the native API are not
> what you look for. Check the RT_SEM object, with rt_sem_create() using
> the S_PULSE flag.
>
Thanks,
i will looking for rt_sem_create and S_PULSE.
Regards
Johann
prev parent reply other threads:[~2013-11-26 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 9:39 [Xenomai] rtdm_event_pulse in user space Johann Obermayr
2013-11-25 9:46 ` Philippe Gerum
2013-11-26 10:50 ` Johann Obermayr
2013-11-26 10:55 ` Philippe Gerum
2013-11-26 11:06 ` Johann Obermayr [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=529480C5.7040901@sigmatek.at \
--to=johann.obermayr@sigmatek.at \
--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.