Please consider if some Native real time objects are created like
“alarm”, by rt_alarm_create() and a real time task by
rt_task_create() and some other objects inside a real time Xenomai
task or inside a regular Linux task and the task ends and finishes
without deleting those objects explicitly.
>
>
>
>
> IIUC, this would add the quite unexpected requirement of having to reopen
> a file for getting fresh data. read() should actually (re-)read the current
> object state each time it is invoked, and not resend some frozen state
> collected by the corresponding open() indefinitely.
>
> e.g. t
>
>
> test code snippet:
>
> static void test_task(u_long a,u_long b,u_long c,u_long d)
> {
> while (1)
> tm_wkafter(1000);
> }
>
> static void main_task(u_long a,u_long b,u_long c,u_long d)
> {
> u_long tid,args[4] = {0,0,0,0};
> int i;
> char name[32];
>
> for (i=0;i<256;i++) {
>
On 10/15/2013 10:50 AM, Kim De Mey wrote:
This patch set adds an initial implementation of registry for pSOS
tasks, semaphores and queues. It is similar as the already existing
vxworks implementation but with more output data.
Important to mention is that the "size" parameter in the read functio
I have two questions:
1) I want to create an alarm object in kernel space and an alarm
handler and then i have a user space task which waits for that alarm
defined inside kernel.
How can i reference the created alarm object by that user-space task?
and how that task is unblocked inside kernel?
2)
