From: dan@ennex1.eng.utsa.edu (Daniel Shelton)
Newsgroups: comp.sys.next.misc
Subject: Re: NeXT DSP memory
Date: 24 Nov 92 03:04:53 GMT
Reply-To: dan@ennex1.eng.utsa.edu (Daniel Shelton)
Organization: Univ of Texas at San Antonio

In article <1es4glINNctc@agate.berkeley.edu> izumi@pinoko.berkeley.edu  
(Izumi Ohzawa) writes:
> In article <1992Nov23.225548.16414@ringer.cs.utsa.edu> dan@ennex1.eng.utsa.edu (Daniel Shelton)  
> writes:
> >In article <1992Nov23.172959.3855@pencom.com> ph@pencom.com (Patrick  
> >Hester) writes:
> >> Does anyone know about adding DSP memory to a (non-turbo) 68040 cube?
> >> I've checked the FAQ but no mention of DSP memory.
> >> I'd like to pump up the DSP so I can have lots of sy 
nthesis going on at
> >> the same time.
> >> So if anyone knows how much memory can be added, what kind, where to
> >> get it, prices or any other clues, please let me know. Also if you
> >> happen to have an idea how extra memory will change the limits...
> >
> > You can add another 32K of memory, they will say 96K, but the DSP
> >memory is 24 bits wide so it is only 32K, to the DSP via a SIMM module
> >from NeXT for $195.  Call them at 1-800-848-NeXT for details. Part
> >#N7013. 
> 
> It will NOT ADD 32kwords of memory -- N7013 will REPLACE the existing
> 8kwords of DSP RAM with 32kwords on a SIMM.  So you end up with the
> total of 32kwords (96kbytes) after installation of N7013, not
> 40kwords = 8 (existing) + 32 (N7013).  I suppose the 8k on the CPU
> board is disabled.
> 
> 
> Also, current 3.0 MusicKit from CCRMA will NOT use the expanded DSP RAM
> automatically.  It is hardcoded for 8kwords (It has always been for
> previous releases).  Therefore, installing N7013 will not automatically
> increase synthesis capacity of a NeXT.   I believe you must obtain the
> MusicKit sources and change the hardcoded DSP RAM size (8k) and re-make
> the kit.  Doc mentions that auto-detection of DSP RAM size is an item
> on the to-do list for future, but not yet supported.
> 
> It is pretty simple to determine whether a NeXT has 8k or 32k of DSP
> RAM at run time, but you need to run a DSP program to do this.
> See DSPMemorySize.tar.Z on the archives.
> 
> --
> Izumi Ohzawa             [ $BBg_78^=;(J ]
> USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
> Telephone: (510) 642-6440     Fax:  (510) 642-3323
> Internet: izumi@pinoko.berkeley.edu (NeXT Mail OK)

Thank you for the correction.

Danmory can be added, what kind, where to
> >> get it, prices or any other clues, please let me know. Also if you
> >> happen to have an idea how extra memory will change the limits...
> >
> > You can add another 32K of memory, they will say 96K, but the DSP
> >memory is 24 bits wide so it is only 32K, to the DSP via a SIMM module
> >from NeXT for $195.  Call them at 1-800-848-NeXT for details. Part
> >#N7013. 
> 
> It will NOT ADD 32kwords of memory -- N7013 will REPLACE the existing
> 8kwords of DSP RAM with 32kwords on a SIMM.  So you end up with the
> total of 32kwords (96kbytes) after installation of N7013, not
> 40kwords = 8 (existing) + 32 (N7013).  I suppose the 8k on the CPU
> board is disabled.
> 
> 
> Also, current 3.0 MusicKit from CCRMA will NOT use the expanded DSP RAM
> automatically.  It is hardcoded for 8kwords (It has always been for
> previous releases).  Therefore, installing N7013 will not automatically
> increase synthesis capacity of a NeXT.   I believe you must obtain the
> MusicKit sources and change the hardcoded DSP RAM size (8k) and re-make
> the kit.  Doc mentions that auto-detection of DSP RAM size is an item
> on the to-do list for future, but not yet supported.
> 
> It is pretty simple to determine whether a NeXT has 8k or 32k of DSP
> RAM at run time, but you need to run a DSP program to do this.
> See DSPMemorySize.tar.Z on the archives.
> 
> --
> Izumi Ohzawa             [ $BBg_78^=;(J ]
> USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
> Telephone: (510) 642-6440     Fax:  (510) 642-3323
> Internet: i
Newsgroups: comp.sys.next.misc