Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!wiml
From: wiml@milton.u.washington.edu (William Lewis)
Newsgroups: comp.sys.next
Subject: Re: Using DSP as a modem
Message-ID: <10722@milton.u.washington.edu>
Date: 7 Nov 90 06:46:50 GMT
References: <10363@ubc-cs.UUCP>
Organization: University of Washington, Seattle
Lines: 25

In article <10363@ubc-cs.UUCP> sritchie@cs.ubc.ca (Stuart Ritchie) writes:
>The idea has been floating around since the beginning, and it's
>a nifty idea alright... but wouldn't this complicate local sound
>a tad?

  Now, what THIS box needs is *2* DSPs! Yeah!     =8)

 ...

>In general, I guess this is a problem of multiple applications trying
>to access the DSP at the same time.  I wonder how this is handled...

    Last I checked, when you reserve the DSP, you specify an arbitration
port or arbitration callback, so that if someone else wants the DSP
while you have it you do know about this and can give it to them if
you want. I doubt they can wrest control without your process' consent,
though. (In the case of beeps, they probably get lost -- try playing a long
soundfile, and beeping. No noise.)


-- 
 wiml@milton.acs.washington.edu       Seattle, Washington   
     (William Lewis)   |  47 41' 15" N   122 42' 58" W  
"These 2 cents will cost the net thousands upon thousands of 
dollars to send everywhere. Are you sure you want to do this?"