MoveSSP

Copies the system's stack from Chip RAM to Fast RAM, generally to be called
as part of one's Startup-Sequence.

Written by Christoper A. Wichura (caw@miroc.chi.il.us)
Created: 3/4/90

Version 1.1 modified by J. Edward Hanway (jeh) - 4/18/90
- Frees the 6K of chip memory used by the original SSP.
- Treats memory outside of 24-bit address space as FAST RAM.
- User Supervisor() instead of SuperState()/UserState() so it can (and should)
  be run ahead of SetPatch 1.34.

This is really a conversion of MoveSSP.c by Roger Uzun into 68k code,
with various `optimizations' being made as well.

The arp library is required to use this program.

It is fully residentiable, though to do so would be stupid as it will
not do anything after the first invocation.

This file supports being called by WorkBench.  However, you will have
to supply your own `.info' file for it (if anyone comes up with a really
nice looking one then UUencode it and send it to me).

I moved it to ML to make it smaller (i.e., no longer needed the Lattice
startup code which eats a bunch of memory up).  I also added some
messages to let you know what has happened, which MoveSSP.c didn't do.

I have not noticed any tremendous speed increase in using this program,
but it can't really hurt.  The people who will get the biggest benefit
from it are those with 32 bit RAM.  The biggest benefit should come when
using lots of interrupts and a DMA-intensive screen, such as using a
16-color terminal program at high baud rates.

It's best to run this thing in your startup-sequence before SetPatch so
that the when the old stack space is freed it can be merged in with the
rest of CHIP RAM. (The SetPatch R option permanently allocates a few bytes
right below the system stack, which fragments the old system stack area
from the rest of CHIP RAM.)