First, thank you jacadcaps and Piru.
With the information provided I can exclude my private speculation! :)
On the other hand it means that somewhere my code is broken, at least
for MorphOS, while it runs fine on classic machines.
Quote:
Note that you should not perform lengthy and/or complex operations in
the softint, and certainly not anything that might result in Wait()
I am aware of (almost) all the pitfalls and limitation that come
along with interrupt code which is (usually) executed in supervisor
mode (m68k). In the past I used one of the four CIA timers to enact
interrupts whenever needed and outsourced medium length code in a
software interrupt code enforced with Cause() within the hardware
interrupt code.
Now I am fiddling around with dynamically adjustable interrupt
periods and I thought that by the timer device caused request would
be a good solution, because the 'time-out' can be applied on the fly
(tr->tr_time.tv_micro = md->timeout).
Because I know now that there is no genuine interrupt caused by the
timer device based SOFTINT, what possibilities do we have in order to
cause such interrupt requests? That's because I really need constant
periods and I would speculate that task based code executed is more
often interrupted than a genuine low-level interrupt code (?).
Thanks in advance.
