www.delorie.com/archives/browse.cgi | search |
From: | "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Physical (device) memory question |
Date: | Sun, 4 Jul 1999 15:36:01 |
Organization: | Aspen Technology, Inc. |
Message-ID: | <377f7f61.sandmann@clio.rice.edu> |
References: | <slrn7nhvtl DOT 3d1 DOT wtanksle AT dolphin DOT openprojects DOT net> |
NNTP-Posting-Host: | ptdemo.aco.aspentech.com |
X-NewsEditor: | ED-1.5.8 |
Lines: | 8 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> I've got to write a test program for one of our PCI cards, and it includes > about 16M of PCI-mapped memory. I'm thinking that > __djgpp_map_physical_memory would work nicely to make that memory easily > accesible to me (is this right?). I suggest using __dpmi_physical_address_mapping - it's a direct call to the DPMI routines. If I remember right the routine you refer to is a wrapper arround the dpmi routine. Either should work if you follow the docs.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |