Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!puff!chin-lon
From: chin-lon@puff.WISC.EDU (Chin-long Cheng)
Newsgroups: comp.sys.amiga
Subject: Re: amiga serial question
Message-ID: <671@puff.WISC.EDU>
Date: Sun, 19-Apr-87 16:03:53 EST
Article-I.D.: puff.671
Posted: Sun Apr 19 16:03:53 1987
Date-Received: Sun, 19-Apr-87 21:36:50 EST
References: <8704190128.AA19495@cory.Berkeley.EDU>
Organization: U of Wisconsin CS Dept
Lines: 20

In article <8704190128.AA19495@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> 
> I would strongly suggest that you use the device instead of
> writing your own interrupt handler.  

But I do need to use my own interrupt handler as the serial.device isn't
fast enough for the midi application that I'm doing. (31.25K with
quite a bit of real time data handling)
> 
> If you want to arbitrate exclusive access, simply have all the tasks use a
> Semaphore or something before doing the operation.  (that is, you still open
> the serial.device with shared access).
> 
I need to do this without using Semaphores, as the tasks would be 
independt and each won't know how many of the others exist. 
So the question remains: how can I coordinate between processes
using serial.device and interrupt handlers?

> 				-Matt
Chin-Long Cheng