🚀 go-pugleaf

I need to service a hardware interrupt using code that (apparently)
can't operate in Supervisor state.  Without the offending call, an
interrupt server works fine, but... I understand I need to use a
handler.

The problem is that I am using a shared interrupt - INTB_PORTS. I don't
see anywhere that interrupt handlers are called by the shared server
handler.

I sure can't just grab the interrupt & go...

Questions:

1) Are INTB_PORTS (shared) interrupts handled by the server handler for
both interrupt servers and interrupt handlers? I.e. can I just fall
through if my board didn't pull the interrupt line & expect everything
else to continue to be serviced when I call an interrupt handler?
(Or moveq #1,d0; when it was mine?)

2) If not, how can I service a shared interrupt asynchronously while in
user state? I can't always Wait().

3) If so, can someone point me to info that documents how to properly
set up an interrupt handler to deal with when it is and isn't mine?

Actually, the ISR needs to operate in two modes: asynchronously and
with signals for when I need to Wait() for the event. My interrupt
server test routine currently does these operations correctly - just
can't accomplish the asynchronous operation mode while in Supervisor.

Thanks,
====================================================================
Kent Polk - Southwest Research Institute - kent@swrinde.nde.swri.edu
        Motto : "Anything worth doing is worth overdoing"
====================================================================