On Tue, Apr 25, 2000 at 02:45:49PM -0700, Oliver King-Smith wrote:
Close to my wish list.
> 1) I love the current memory protection scheme, but, if you could improve
> the performance of DmWrite (and cousins) it would allow developers to take
> greater advantage of the memory architecture.
A CPU32 or 68010 core has a loop mode, so it would be a lot faster to
set or copy any memory. (loop mode does no opcode fetches after the
move and the dbcc). Motorola already has these in their silicon
library. A 68020 core (if it had the barrel shifter) would speed up
graphics, and the 68030 would allow for MMU type things.
Actually a 68010 with the restartable bus error would allow for MMU
type things (unless Dave Small's Magic Sac [mac emulation for the
Atari ST] 68000 restart code would work).
> 2) The floating point performance is limited on the current 68K. While
> people often say this is a specialized application, it is useful for both
> scientific as well as consumer applications, (such as wireless and
> compression).
Coprocessor. But I was thinking DSP, but maybe DSP/FPU/MMX?
> 3) Getting protection for OS globals so people like me don't accidently
> stomp them.
Good point, but couldn't they be moved to a fixed DmWritable location
just above the dynamic heap curtain (increasing both the dynamic heap
and safety).
> 5) Keep the power consumption low.
And the elegant simplicity of the design in all the aspects. And the
cost within reason. (Could they halve again the size of the V?).
I would just add the sound and the higher rez timing I mentioned earlier.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
