"Stephen D. Cohen" wrote:
>
> Victor Et. Al.,
>
> You recently wrote:
>
> > 1. Saving fp state is _slow_ so you don't need it in an ISR
> > -- there is no performance loss
> > in having the ISR hand over work to a thread.
>
> I have been trying to figure out how to do this for some time.
> Would you please provide a code fragment or clear explanation of how to have
> an ISR cause a thread to become computable?
>
> I thought it would be correct to simply have the thread sleep until
> it gets woken up by the ISR, but I am told that this will cause the thread
> to run in the ISR context. That is, obviously, not what we want. I want to
> get in and out of ISR context just as quickly as possible, but cause another
> thread to become computable (a high priority hardware handler responding to
> the interrupt, for example).
>
> Any suggestions?
>
> Confusedly Yours,
>
Hi Stephen,
I may be mistaken, but I think in RTAI/RTL, you can set a semaphore from
within the ISR, exit and on exit the real-time task/thread will run its
code. If it doesn't work this way, it would be nice to have this
facility available as this is typical of the sort of thing I used to do
with pSOS.
Regards, Stuart
-- [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/
