Lpc2000

Sorry about the overpost thing.  I don't use Mail Groups very often, and
News Groups have got me spoiled
to that point :).

>  Maybe you might rethink your requirements and adjust your parameters 
>  accordingly.

I had thought of using something as a driver chip, but everything I've
found is either too costly,
over my head as far as skills go, or depricated.  Course then again this
may be over my head 
too :).  Honestly I didn't figure that VGA could be that difficult since
the old 8088's could do it 
and still have time to pull off simple graphics.  Maby an FPGA as a
driver would be better,
but my lack of knowledge in this section of the world puts me at a great
disadvantage.

Course thats where my confusion is.  I figured that the display update
cycles wern't going
to be all that bad.  So I would have plenty of time to read from the SPI
bus to get the next
segment of the screen.  Guess I was wrong.

Do you tink its possiable to pull off full screen grapics with the 2138?
 I figured it took:
2457600 bits or 307,200 bytes to store a screen.  Since the 2138 has
512k bytes
I could store a full screen and still have 201,800 bytes for code.  I
also figured that
I could cheat and use two of the PWM channels to handle the H-Sync and
V-Sync
signals, thus lowering the overhead again.  For image switching I would
simply point
to a blank screen, load over my image buffer and then point back.  It
sounds like
this won't be the case :).  I'm quite new to all of this ARM stuff, only
done AVR's
in the past, and I have to admit I have probiably bitten off more then I
can chew at the
moment.

Jeremy