Hello Olaf,
Where you're using mode 2 of comedi data acq, comedi will take care of
calling 'callback'. 'callback' will awaken you're rt_thread, and
everything will work nicely...
if, you remove the lines where you set the rt_thread periodic.
pthread_make_periodic_np(?) would be required if you were
using mode 0 in comedi, and you wanted the cpu to trigger the board,
as opposed to the other way around.
Cheers-Chuck
However, by setting rt_thread as periodic, the system is trying
to wake it up at the same frequency that comedi is trying to wake
it up.
On Fri, 29 Sep 2000, Olaf Petzold wrote:
> Hallo,
>
> attached is a piece of code where I want to aquire data using comedis callback
> function. After insmod the module I can read the last message set "FP on
> thread" and than the system reboots or is frozen.
>
> IMO I have to use the oneshot mode ( As I right remember I have to use
> HRTIME_INFINITY as period) for the thread. This is wakeup() by the callback and
> gets suspended by pthread_suspend_np. rtl_schedule() is done by this function
> itself- see the source on RTL.
>
> In period mode with 1 Hz and pthread_wait_np() the thread_code seems to work
> well.
>
> What it's going here and where is the fault, please help. The reason why I'm
> using threads is the use of fp inside for later use. If I'm right, that I can't
> use fp inside a normal kernel module ?
>
> Thanks Olaf
>
>
>
-- [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/
