Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!umd5!brianf
From: brianf@umd5.umd.edu (Brian Farmer)
Newsgroups: comp.windows.ms
Subject: Re: Accessing memory mapped boards in 3.0 386 mode?
Message-ID: <6616@umd5.umd.edu>
Date: 5 Jun 90 14:10:01 GMT
References: <5660@hub.ucsb.edu>
Reply-To: brianf@umd5.umd.edu (Brian Farmer)
Organization: University of Maryland, College Park
Lines: 14

In article <5660@hub.ucsb.edu> grosen@amadeus.ucsb.edu (Mark D. Grosen) writes:
>
>Well, still no sign of the 3.0 SDK.  Meanwhile, I am curious to know how
>memory mapped peripherals are accessed in 3.0's 386 protected mode.
>Judging from the behavior of my old programs that access a hunk of
>shared memory at 0xd0000, making a far pointer in 3.0 is a no-no.  Is there
>something similar to Unix's "physical I/O" functions that let you specify
>an absolute address?  
>


A few global selectors have been defined to directly access the
memory.  They are __A000H, __B000H, __B800H, __C000H, __D000H,
__E000H, __F000H.