Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!spool.mu.edu!bloom-beacon.mit.edu!gatech!prism!gt8134b
From: gt8134b@prism.gatech.EDU (Howlin' Bob)
Newsgroups: comp.os.386bsd.development
Subject: Re: V86 mode & the BIOS (was Need advice: Which OS to port to?)
Message-ID: <109151@hydra.gatech.EDU>
Date: 17 Aug 93 18:56:31 GMT
References: <107181@hydra.gatech.EDU> <1993Aug4.073826.24956@fcom.cc.utah.edu> <107725@hydra.gatech.EDU> <1993Aug9.224939.19834@fcom.cc.utah.edu> <108137@hydra.gatech.EDU> <BLYMN.93Aug12205126@mallee.awadi.com.au>
Organization: Georgia Institute of Technology
Lines: 16
In <BLYMN.93Aug12205126@mallee.awadi.com.au> blymn@awadi.com.au (Brett Lymn) writes:
>Unfortunately, the v86 call is not a simple in *BSD, the method Linux
>uses to change the task into v86 mode will not work due to differences
>in the way the supervisor stack is used in *BSD (this is from memory,
>I may have the wrong names but the concept is right I think).
Hmm. All you have to do to enter V86 mode is to set the VM bit in
the EFLAGS saved register. Are you saying that the kernel cannot
modify the process's saved EFLAGS?
--
Robert Sanders
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt8134b
Internet: gt8134b@prism.gatech.edu