Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: amiga serial question
Message-ID: <8704190128.AA19495@cory.Berkeley.EDU>
Date: Sat, 18-Apr-87 20:28:47 EST
Article-I.D.: cory.8704190128.AA19495
Posted: Sat Apr 18 20:28:47 1987
Date-Received: Sun, 19-Apr-87 08:24:17 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 14


	I have never had problems with the EXEC serial.device ... especially 
with 1.2 .  I would strongly suggest that you use the device instead of
writing your own interrupt handler.  Most people's problems with the
serial.device is from a lack of understanding of how it works rather than
bugs in the actual device.

	Assuming you use the EXEC serial.device, having multiple tasks writing
to the serial port at the same time is trivial... they just do it.
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).

				-Matt