Hello all we are porting a mcf5282 uClinux multi-threaded software
from the 2.4 stuff to the 2,.6.x framework, our timing facilities
seems quite close to the POSIX.4 timers specifactions, to be confident
we have create some test programs to fully understand the provided
functionalities and our present requirements on the main application.
The probe stuff has been initially built under the x86-glibc-2.6.
chain
but the point is that the execution of the cross-compiled version for
mcf5282-uclibc-2.6 stuff is really weird.
I have checked the uclibc library rt functionalities and i have
noticed about the next line on the timer_create symbol entry:
/* Notification via a thread is not supported yet */
if (__builtin_expect(evp->sigev_notify == SIGEV_THREAD, 1))
return -1;
which will smoothly FAIL, cause any value is assigned to errno
Could anybody tell me something else about this missed feature?
Compliance with the Murphie's law this is the mechanism that we have
chosen to feedback the timer expiration event so we would like to know
also where should we check this issues to prevent future
mistakes/misunderstandings
Cheers..
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
