Re: rt_task_unblock() POSIX alternative

On Tue, Apr 7, 2020 at 5:18 PM Petr Červenka via Xenomai wrote: > > Hello Jan. > And if I don't want to totally remove the thread? Only to interrupt the > waiting and react according to new events (like reconfiguring something or > starting to wait on different resource). > Is there some

Re: rt_task_unblock() POSIX alternative

On 07.04.20 17:18, Petr Červenka wrote: Hello Jan. And if I don't want to totally remove the thread? Only to interrupt the waiting and react according to new events (like reconfiguring something or starting to wait on different resource). Is there some pthread_create... or sched_... parameter

Re: rt_task_unblock() POSIX alternative

Hello Jan. And if I don't want to totally remove the thread? Only to interrupt the waiting and react according to new events (like reconfiguring something or starting to wait on different resource). Is there some pthread_create... or sched_... parameter or flag, that the task's system call can

Re: rt_task_unblock() POSIX alternative

On 07.04.20 15:41, Petr Červenka via Xenomai wrote: Hello everyone. I there a rt_task_unblock() Xenomai POSIX skin alternative? I created an example of periodic POSIX task, similar to the latency example but with very long period. When I receive a INT signal I set the end flag and I would like

rt_task_unblock() POSIX alternative

Hello everyone. I there a rt_task_unblock() Xenomai POSIX skin alternative? I created an example of periodic POSIX task, similar to the latency example but with very long period. When I receive a INT signal I set the end flag and I would like to unblock a task that waits on read(timerfd). But

Re: Is anybody can show me a simple rtdm driver to read/write virtual memory device?

Thanks, I'll check it out. Pierre FICHEUX 于2020年4月7日周二 下午6:34写道： > Hi, > > I wrote some RTDM examples for Pi 3 GPIO (based on BCM register access, > not GPIO kernel API). > > May be it could help... > > regards > > Le lun. 6 avr. 2020 à 09:45, Jan Kiszka via Xenomai > a écrit : > >> On

Re: Is anybody can show me a simple rtdm driver to read/write virtual memory device?

Hi, I wrote some RTDM examples for Pi 3 GPIO (based on BCM register access, not GPIO kernel API). May be it could help... regards Le lun. 6 avr. 2020 à 09:45, Jan Kiszka via Xenomai a écrit : > On 06.04.20 09:22, 孙世龙 via Xenomai wrote: > > Is anybody could show me a simple xenomai3 rtdm

Re: Is anybody could tell me the relation between lib/boilerplate folder and lib/copperplate folder?

On 07.04.20 11:40, 孙世龙 via Xenomai wrote: Is anybody could tell me the relation between lib/boilerplate and lib/copperplate? I am using xenomai-v3.1. Thanks a lot.Looking forward to your replay. libboilerplate: internal utility services, used across the board, also both by cobalt and

Re: Does the function malloc() uses the real malloc or the wrap one in heapobj_pkg_init_private(）.

On 07.04.20 11:13, 孙世龙 via Xenomai wrote: The source code url is https://gitlab.denx.de/Xenomai/xenomai/-/blob/v3.1/lib/copperplate/ heapobj-heapmem.c line:107 In the source code listed above, function heapobj_pkg_init_private() calls malloc(). I hope to know whether it calls the wrapper

Is anybody could tell me the relation between lib/boilerplate folder and lib/copperplate folder?

Is anybody could tell me the relation between lib/boilerplate and lib/copperplate? I am using xenomai-v3.1. Thanks a lot.Looking forward to your replay.

Does the function malloc() uses the real malloc or the wrap one in heapobj_pkg_init_private(）.

The source code url is https://gitlab.denx.de/Xenomai/xenomai/-/blob/v3.1/lib/copperplate/ heapobj-heapmem.c line:107 In the source code listed above, function heapobj_pkg_init_private() calls malloc(). I hope to know whether it calls the wrapper function or the real malloc function which