[Xenomai] rtdm_event_pulse in user space

[Xenomai] rtdm_event_pulse in user space

[Johann Obermayr]

Hello,

Is there a way to make a
rt_event_pulse.
A kernel function  rtdm_event_pulse is available, but no user space 
function.

Thanks.

Best Regards
   Johann

Re: [Xenomai] rtdm_event_pulse in user space

[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.

-- 
Philippe.

Re: [Xenomai] rtdm_event_pulse in user space

[Johann Obermayr]

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.

Best Regards
    Johann

Re: [Xenomai] rtdm_event_pulse in user space

[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.

-- 
Philippe.

Re: [Xenomai] rtdm_event_pulse in user space

[Johann Obermayr]

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