Stimulus driven interrupts?
Posted: Wed May 05, 2021 9:46 pm
In this Oberon-1 paper (http://norayr.am/papers/WirthTasksVersusThreads.pdf) from 1996, Wirth discusses a method of "real-time tasks". (Page 10). In which I believe interrupt handlers installed with Kernel.Instal(Handler, N) are triggered when a device or buffer is updated?
I see that Kernel.Install still exists in the RISC5 source. Can this method still be used for "real-time tasks" in which a procedure is run when an external stimulus changes? So far all the interrupt examples I've seen make use of interrupts triggered periodically by the millisecond timer, but I'm a little out of my depth here so it's very possible I missed something
My end goal is to trigger an interrupt (from firmware or otherwise) without having to wait for the millisecond timer
I see that Kernel.Install still exists in the RISC5 source. Can this method still be used for "real-time tasks" in which a procedure is run when an external stimulus changes? So far all the interrupt examples I've seen make use of interrupts triggered periodically by the millisecond timer, but I'm a little out of my depth here so it's very possible I missed something
My end goal is to trigger an interrupt (from firmware or otherwise) without having to wait for the millisecond timer