Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!kent
From: kent@swrinde.nde.swri.edu (Kent D. Polk)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Shared Interrupt Handlers
Message-ID: <21415@swrinde.nde.swri.edu>
Date: 19 Sep 89 13:25:43 GMT
References: <21387@swrinde.nde.swri.edu>
Reply-To: kent@swrinde.UUCP (Kent D. Polk)
Organization: Southwest Research Institute, San Antonio, Texas
Lines: 27

In article <21387@swrinde.nde.swri.edu> kent@swrinde.nde.swri.edu (Kent D. Polk) writes:
>
>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.
[...]
>2) If not, how can I service a shared interrupt asynchronously while in
>user state? I can't always Wait().

I see I have used the term asynchronously a bit too lightly. I had
thought of setting up a separate task which could be signaled to
perform the service & it could also signal the main task when
necessary, but I really shouldn't have two tasks talking to my device.
In fact, after thinking about it a bit more I am even more confused
about how to go about accomplishing what I want. So, it's back to the
drawing board...

I still would like to know if interrupt handlers can be inserted into a
shared handler's linked list & yet operate in user mode - I don't see
how that would be possible given my understanding of how things work.

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