Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ames!lll-tis!ptsfa!well!ewhac
From: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Newsgroups: comp.sys.amiga
Subject: Amiga MIDI design philosophy (was Re: Amiga midi problems?)
Message-ID: <3819@well.UUCP>
Date: Tue, 25-Aug-87 18:07:35 EDT
Article-I.D.: well.3819
Posted: Tue Aug 25 18:07:35 1987
Date-Received: Thu, 27-Aug-87 05:54:44 EDT
References: <1408@ico.UUCP> <1601@ulowell.cs.ulowell.edu> <628@cup.portal.com> <533@sugar.UUCP> <2247@cbmvax.UUCP>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: The NSC (North's Shredding Continues)
Lines: 23
Summary: Use the interrupt handler to do the timestamping.

In article <2247@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
>The Amiga serial.device does not timestamp the serial input events.  [...]
>The solution ?
>There are two...(I like this one) write a small, very fast
>midi.device (which can leave out a lot of stuff the serial.device
>has to keep around) or set up a small task, running at a high
>priority, whose task it is to get bytes from the serial.device,
>timestamp them, and feed them to whoever asks.  (through a message port)
>
	No, don't use a task to timestamp the serial events; the switching
time is too slow, as well as running the risk of being pre-empted.

	Write an interrupt handler who grabs the bytes off the serial port,
timestamps them, puts them im a buffer, and signals the main .device driver.

	I mention this in case anyone decides to actually go out and do
this; just want to be sure it gets written is the most effective way.

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	ihnp4!ptsfa -\
 \_ -_	 Bike shrunk by popular demand,	      dual ---> !{well,unicom}!ewhac
O----^o	 But it's still the only way to fly.  hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor