Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!ucsdhub!hp-sdd!hplabs!hpl-opus!hpspdra!ric
From: ric@hpspdra.HP.COM (Ric Peregrino)
Newsgroups: comp.sys.amiga
Subject: Re: Come on PEOPLE...
Message-ID: <13570022@hpspdra.HP.COM>
Date: 21 Feb 90 20:17:53 GMT
References: <1990Feb12.223912.7167@ug.cs.dal.ca>
Organization: HP Stanford Park - Palo Alto, CA
Lines: 28


No need to take back everything you said about Europeans.
I'm from the USA.

What's wrong with using the hardware manual to get a job done.

I thought about this serial problem and the only solution that
might be portable would be to make a board with about 512 kbytes
of buffer and let it listen to the port continuously. Here a 
driver would interface the board to the AMIGA "correctly".

This would be a big job, but it could work faster. 614kbaud is
the max data rate from a Yamaha TX16W sampler. (RS422)

In reading the RKM I found a statement saying that one should
not disable interupts for more than 250us. My routine violated
this but it exited gracefully; at least with no other active 
processes. Does any one know the underlying reason for the 250us?

How about comments on a "cleaner" way of interfacing to MIDI 
without losing data on large data dumps (hundreds of kilobytes).
10 bits at 31.25kps (start+8+stop) is 320us. I noticed the 
RBF interupt is priority 6. How long does it take between an 
interupt to when service routine gets CPU? 

"damn the torpedos"
ric@hpspd