Date: Sun, 28 Feb 1999 14:36:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "v. straka" <vstraka AT iol DOT cz>
cc: djgpp AT delorie DOT com
Subject: Re: __dpmi_physical_address_mapping
In-Reply-To: <01be61b5$4c6ae000$7b7b7b7b@celeron>
Message-ID: <Pine.SUN.3.91.990228143631.5950a-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On 26 Feb 1999, v. straka wrote:

>   VESAmapping.address = mode_info.PhysBasePtr;
>   VESAmapping.size = vesa_info.TotalMemory << 16;
>   /* Why __dpmi_physical_address_mapping change VESAmapping.address ?!!!
>      -> I mapped address X and then set selector to address Y */
>   if (__dpmi_physical_address_mapping(&VESAmapping) != 0) return -1;

Did you read the docs of this function?  That's exactly what it's
supposed to do.  Here's what the library reference says:

  Maps a physical device (like a graphics buffer) to linear memory.  Fill
  in the physical address and size (in bytes).  On return, the address is
  the linear address to use.