Return to BSD News archive
Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!mcsun!sun4nl!relay.philips.nl!cnplss5.cnps.philips.nl!bashful.isp.cft.philips.nl!rooij
From: rooij@bashful.isp.cft.philips.nl (Guido van Rooij)
Subject: Re: V86 mode & the BIOS (was Need advice: Which OS to port to?)
Message-ID: <1993Aug12.070617.10945@cnplss5.cnps.philips.nl>
Sender: news@cnplss5.cnps.philips.nl (USENET News System)
Organization: Philips Communications & Processing Services, Eindhoven
References: <107725@hydra.gatech.EDU> <1993Aug9.224939.19834@fcom.cc.utah.edu> <108137@hydra.gatech.EDU> <1993Aug10.195941.17468@fcom.cc.utah.edu> <108354@hydra.gatech.EDU>
Date: Thu, 12 Aug 1993 07:06:17 GMT
Lines: 19
gt8134b@prism.gatech.EDU (Howlin' Bob) writes:
>In <1993Aug10.195941.17468@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>>In article <108137@hydra.gatech.EDU> gt8134b@prism.gatech.EDU (Howlin' Bob) writes:
>>>>This implies (I believe) an I/O map per process -- kinda messy, and a
>>>>generally bad thing if two devices live in the same page. The best of
>>>
>>>Yes, the Linux TSS has an I/O bitmap large enough to map the I/O
>>>addresses from 0 to 0x3ff. 128 bytes is not too high a cost, really.
>I have come to understand that {386,Net,Free}BSD do not use the 386
>hardware task switching. Could someone explain why? More importantly,
>is one systemwide TSS used for all processes?
Yes. That's correct. And even in this one and only TSS, the pointer to the
io permission bitmap was not set up properly!!
-Guido