Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: V86 mode & the BIOS (was Need advice: Which OS to port to?) Message-ID: <hastyCBLnIF.Cyq@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <1993Aug4.073826.24956@fcom.cc.utah.edu> <107725@hydra.gatech.EDU> <245jrfINNrc0@bonnie.tcd-dresden.de> Date: Wed, 11 Aug 1993 14:42:14 GMT Lines: 32 In article <245jrfINNrc0@bonnie.tcd-dresden.de> j@bonnie.tcd-dresden.de (J Wunsch) writes: >In <107725@hydra.gatech.EDU> gt8134b@prism.gatech.EDU (Howlin' Bob) writes: >>can use them), but all this is done by the Linux ioperm() system >>call, which makes use of the 386's TSS I/O bitmap field. > >Does this mean, you've a 64 K IO bitmap there? If so, process context >switch must be terribly slow. If not, what do you do with those recent >grafx adaptors that care to use IO ports above 0x3ff? No, the process header block can be specified to be a certain size less than 64k. I did it for the very first port of X11R5 to 386bsd. The mods were done against Pace William's port of X11R5 to a pre-386bsd release. I am very interested on having a dosemu box for 386bsd. I am tired of initializing S3 cards and extracting the info from S3 like if I was a dentist pulling a teeth out of a patient not under anestesia. However, this approach of i/o bitmap permission is not adequate for S3 cards or 8514/a cards. the cards have a sparse i/o range. The highest address is 0xe2e8 or there abouts. Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/incoming