Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!taco!hobbes.catt.ncsu.edu!kdarling
From: kdarling@hobbes.catt.ncsu.edu (Kevin Darling)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: 8-bit death
Message-ID: <1991May4.203526.18142@ncsu.edu>
Date: 4 May 91 20:35:26 GMT
References: <1991Apr30.112820.2451@sugar.hackercorp.com>  <1991May1.064455.3058@kessner.denver.co.us> <21135@cbmvax.commodore.com>  <1991May3.041705.9907@kessner.denver.co.us> <21216@cbmvax.commodore.com>  <1991May3.220043.28760@ncsu.edu> <91124.131359DXB132@psuvm.ps
Sender: news@ncsu.edu (USENET News System)
Organization: North Carolina State University
Lines: 18

DXB132@psuvm.psu.edu writes:
>In article <1991May3.220043.28760@ncsu.edu>, kdarling@hobbes.catt.ncsu.edu
>(Kevin Darling) says:
>>
>>Hey, blame _Motorola_ for the 64K offset limits on a 68000 <g>.  "Pure"
>>(reentrant) code for the Amiga OS has the same data offset limitations.
>
>It doesn't help, but the '020 and higher offer full 32-bit offsets...

Yah, but still wish they'd started off that way.  Ah well.  The only
other slight disappointment I ever had was with the 68008... I think
it should've been able to use non-aligned data/code.  Many years back
I homebrewed a 68008 coprocessor for my old CoCo I.  It had its own
8K static RAM, but also full access to the coco's ram and i/o space
during internal 6809 cycles (the AVMA multiprocessor line on the '09
was perfect for this).  Sure could clear the screen fast! <g>  But
the word-alignment thingie kept me from having more, and easy, fun.
  them were the hacking days, eh? - kev <kdarling@catt.ncsu.edu>