delorie.com/archives/browse.cgi | search |
From: | wtanksle AT dolphin DOT openprojects DOT net (William Tanksley) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Physical (device) memory question |
Message-ID: | <slrn7nhvtl.3d1.wtanksle@dolphin.openprojects.net> |
User-Agent: | slrn/0.9.5.3 (UNIX) |
Lines: | 12 |
Date: | Tue, 29 Jun 1999 17:17:41 GMT |
NNTP-Posting-Host: | 24.4.83.145 |
X-Complaints-To: | abuse AT home DOT net |
X-Trace: | news.rdc1.sdca.home.com 930676661 24.4.83.145 (Tue, 29 Jun 1999 10:17:41 PDT) |
NNTP-Posting-Date: | Tue, 29 Jun 1999 10:17:41 PDT |
Organization: | @Home Network |
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?). How do I know what to pass as the first parameter, the void *our_addr? Does it have to be allocated memory, or does it have to be unallocated? Or does it have to be out of the range of any memory actually usable (such as (void*)(0x01000000))? -- -William "Billy" Tanksley
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |