Hi Paolo,
I do not think that I have to do this as it is an ISA interrupt that is
afterwards forwarded to Linux. Interrupts occur and the system still
runs (no crash!)
also when process ''loop'' is no more waked up (cooperative scheduling
and
scheduling on events like ioctls or so!?) Everything runs ok when I
simply remove
the dummy spin thread, which is strange as I think.
But to be sure about that what I said, I removed the
rtl_global_pend_irq() and inserted
rtl_hard_enable_irq(irq) after the sem_post() call. The behaviour
remains the same.
(BTW, the interrupt is enabled by the device driver of my timer.)
Any idea?
Cheers,
Stephan
Paolo Mantegazza wrote:
>
> Hi Stephan,
>
> check who unmasks and ack the interrupt handler to reanable that and
> lower priotity interrupts?.
>
> I've seen nothing of that kind done in before exiting your handler, and
> it is possible that RTL will not do it for you.
>
> Ciao, Paolo.
-- [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/
