Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!turnkey!orchard.la.locus.com!fafnir.la.locus.com!dana From: dana@locus.com (Dana H. Myers) Newsgroups: comp.arch Subject: Re: What's in the '586? Message-ID: <1991May30.042450.2811930@locus.com> Date: 30 May 91 04:24:50 GMT References: <5814@goanna.cs.rmit.oz.au> <1991May18.161515.22428@leland.Stanford.EDU> <1991May21.191242.4591@sbcs.sunysb.edu> <1991May22.014604.13983@ims.alaska.edu> <1991May24.153126.1468@ichips.intel.com> Organization: Locus Computing Corporation, Inglewood, CA Lines: 20 In article jpc@fct.unl.pt (Jose Pina Coelho) writes: > >In article <1991May24.153126.1468@ichips.intel.com> >chrisj@pdx041.intel.com (Chris Jones) writes: >> 2) REAL mode might be a thing of the past if not for... well, you know. >If not for messy dog, but how would you load the tables for PM ? Easy, the CPU comes up in protected with the on chip descriptors initialized to some well known values which allow access to the entire chip address range. Until you force a descriptor reload by loading a segment register or intersegment jump/call, these values would be in effect. This is how the 80376 works. The 80376 is a 386 without real mode, Virtual/86 mode, or a paging unit. -- * Dana H. Myers KK6JQ | Views expressed here are * * (213) 337-5136 | mine and do not necessarily * * dana@locus.com | reflect those of my employer *