Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!shadooby!accuvax.nwu.edu!tank!ncar!unmvax!tut.cis.ohio-state.edu!bloom-beacon!apple!bbn!bbn.com!slackey
From: slackey@bbn.com (Stan Lackey)
Newsgroups: comp.arch
Subject: Re: looking for >32-bit address space
Message-ID: <38340@bbn.COM>
Date: 6 Apr 89 13:56:48 GMT
References: <1032@myrias.UUCP> <1989Apr3.164538.277@utzoo.uucp> <2516@scolex.sco.COM>
Sender: news@bbn.COM
Reply-To: slackey@BBN.COM (Stan Lackey)
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 19

In article <2516@scolex.sco.COM> seanf@scolex.UUCP (Sean Fagan) writes:
>In article <1989Apr3.164538.277@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>>In article <1032@myrias.UUCP> cmt@myrias.UUCP (Chris Thomson) writes:
>>>Are there any micros or chipsets out there that support an address space
>>>larger than 32 bits? ...
>>And please, let us not hear solemn pronunciamentos about the supposed
>>40-bit address space of the RT -- it has a 32-bit address space, plus
>>8086ish bank-switching.
>The 8086 doesn't bank-switch.  The Apple //e bank switches.  The 8086 uses 

The original request was for a greater-than-32 bit address space, not
some hack segmentation.  Apparently, the requester wanted to spend his
time programming, not hacking around compile and runtime errors
re-partitioning his data.  Anybody can put a map RAM on a micro to
[apparently] extend its addressing.  Hopefully, one or more of the
suppliers will take a leadership role by providing a true larger
addressing feature.  (Hopefully 64 bits.)  And auto-inc addressing and
unaligned data!  Oops sorry.
:-) Stan