David, thanks for your input, but i am a little lost on how to proceed.
I wrote:
>>i would like to generate and store my load reference
> > trajectories in kernal mode.
David asked:
> That is, you want your kernel RTL "driver" to load and verify data that
it'll
> use for the operation...?
I want to do the operations in kernal space because i really do not want the
user space to have access to my load request data. It just is too easy to
get out of control and smash things. It doesn't have to be real time, maybe
i could do what i want with IOCtl?
I asked:
>>My thought is that i
> > would like to use a fifo to communicate, but not do all the setup and
> > verification in the controller itself. The only thing i don't really
have a
> > plan for is how to wake up the task that changes trajectories. Can a
real
> > time thread wait on a fifo?
>
David replied:
> Well, it can be done, but I've been too busy to keep up, so I don't know
if
> it's readily availabe in the current versions. Anyway, an alternative is
to use
> a handler that wakes the RTL thread up when there is [enough] data
available.
This is what i want, but i can't seem to figure out the mechanism to do it.
> > I guess the controller could check the fifo,
> > but how does the controller wake up the "changer thread" so that it runs
> > asynchronously to the controller?
>
> I'm not sure what you mean by "asynchronously" in this context, but sure,
the
> controller (interrupt handler?) could activate/deactivate the periodic
> scheduling of RTL threads and that kind of stuff.
What I meant by asynchronously was that the setup and verification may span
more than one interrupt cycle( it doesn't happen very often so it isn't that
big a deal).
I just would rather worry about synchronization between two tasks than to
worry about relatively large execution times for my interrupt handler.
eric
-- [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/
