Cory Papenfuss ([EMAIL PROTECTED]) wrote:
> I had the same problem when I tried to initialize a thread with
> pthread_setfp_np() in the init_module() portion of module. As near as I could
> tell, once I pthread_create()'d the module, even though the very next line was
> to enable fp, the thread had tried executing fp code before it was enabled to
> do so. I inserted a pthread_suspend_np() in the thread and
> then a pthread_wakeup_np() in the init and it seemed to work around it.
Right. pthread_create starts the task immediately -- unlike old rt_tast_init.
> BTW, is this a silly thing to do? What's the correct order to create threads
> and set their parameters if not?
Calling pthread_setfp_np(pthread_self(), 1) at the beginning of
the thread body.
Michael.
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
