[Coco] The Definitive Post on the CC-Five ;)

[Joel Ewy]

I realize it's far off, but since you mentioned the idea of improving
the CPU, I wonder about the possibility of integrating the MMU/DAT with
the 6x09 in such a way that concatenated index registers could be used
as pointers into a much larger, linear address space.  So perhaps Z is a
new virtual 32-bit address register composed of X and Y.  This won't
affect the stack on interrupts, etc.  But it would allow you to directly
manipulate data structures larger than 64K, as the 32-bit address can be
fed directly into the MMU/DAT, and blocks mapped temporarily in for the
duration of the instruction.  Obviously there would still be code size
limitations.  But if we have big graphcs, big audio, etc, it would be
nice to have big pointers.

JCE

jdaggett at gate.net wrote:
> Mark
>
> Just a thought on expanding the vector table should there be an improvement to the CPU. 
> There are 16 bytes there that are not used and an expanded vector table would be nice. 
>
> Also could put a RTC in at FF80 to FF8F, another block 16 bytes that are not used. 
>
> james
>
> On 29 Jan 2007 at 11:40, Mark McDougall wrote:
>
>   
>> jdaggett at gate.net wrote:
>>
>>     
>>> Also some things I wanted to do is to increase the vector table from
>>> $FFF1 down to $FFE0. At $FFF0/$FFF1 would be the 6309 trap vector,
>>> and then use $FFE0 to $FFEF as vectors for PS2 Keyboard, PS2 Mouse,
>>> and any other 6 vectors deemed necessary. 
>>>       
>> So the PS/2 keyboard won't map to the Coco keyboard? Is that so you
>> can use all the keys on a PC keyboard?
>>
>> Regards,
>> Mark
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.432 / Virus Database: 268.17.12/655 - Release Date:
>> 1/28/2007 1:12 PM
>>
>>     
>
>
>
>