Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!wuarchive!uunet!mcsun!cernvax!chx400!bernina!neptune!inf.ethz.ch!brandis From: brandis@inf.ethz.ch (Marc Brandis) Newsgroups: comp.arch Subject: Re: What's in the '586? Message-ID: <29025@neptune.inf.ethz.ch> Date: 29 May 91 05:51:38 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> Sender: news@neptune.inf.ethz.ch Reply-To: brandis@inf.ethz.ch (Marc Brandis) Organization: Departement Informatik, ETH, Zurich Lines: 18 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 ? If would not be a problem to load the tables if you define the initial values in the segment shadow registers. Assume that all segments would point to some segment at a given physical address (e.g. 0), have a given limit (e.g. 4 Gigabytes) and some reasonable protection settings. Now define that interrupts are disabled after reset. The first thing that you could do were to setup the tables that you need. Marc-Michael Brandis Computer Systems Laboratory, ETH-Zentrum (Swiss Federal Institute of Technology) CH-8092 Zurich, Switzerland email: brandis@inf.ethz.ch