delorie.com/archives/browse.cgi | search |
Date: | Sat, 1 Apr 2000 06:18:37 +0500 |
Message-Id: | <200004010118.GAA01113@midpec.com> |
From: | prashant_tr AT yahoo DOT com (Prashant TR) |
To: | djgpp AT delorie DOT com |
In-reply-to: | <05d34b2c.fc4eeff7@usw-ex0105-036.remarq.com> (message from |
batchex on Thu, 30 Mar 2000 12:06:59 -0800) | |
Subject: | Re: VBE question |
References: | <054a4830 DOT 80e90c42 AT usw-ex0105-036 DOT remarq DOT com> <200003300638 DOT LAA00861 AT midpec DOT com> <05d34b2c DOT fc4eeff7 AT usw-ex0105-036 DOT remarq DOT com> |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
batchex <thedark1NOthSPAM AT phreaker DOT net DOT invalid> proclaimed: > Yes it is. But IMHO, __djgpp_map_physical_memory is doing the > similar thing as the DPMI function. My question is, how to use > the address returned by those functions. I don't see any address being returned in __djgpp_map_physical_memory. You just have to use the our_addr field to access the address you need. Please read the documentation in libc.info ("info libc alpha"). So if you need to access the physical address phys_addr, use x = our_addr[0]; __djgpp_map_physical_memory(void *our_addr, unsigned long num_bytes, unsigned long phys_addr);
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |