Message-ID: <001701bf690e$754e7d40$c71b15c8@telecomco.net>
From: "Julian Rolon" <jrolon AT alpha DOT telecom-co DOT net>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: <djgpp AT delorie DOT com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000127191152 DOT 19181C-100000 AT is>
Subject: RE: DMA access
Date: Thu, 27 Jan 2000 15:35:35 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Reply-To: djgpp AT delorie DOT com


----- Original Message -----
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Julian Rolon <jrolon AT alpha DOT telecom-co DOT net>
Cc: <djgpp AT delorie DOT com>
Sent: Thursday, January 27, 2000 11:13 AM
Subject: Re: DMA access


>
> On Thu, 27 Jan 2000, Julian Rolon wrote:
>
> > faq states two methods for correct DMA accessig, one of these is =
> > allocate a buffer in conventional memory with DPMI function =
> > allocate_dos_memory but this function return a real mode segment between
=
> > 0000 and FFFF, How can i guarantee that segment returned falls into =
> > Conventional memory??
>
> The function __dpmi_allocate_dos_memory, by its very definition, *always*
> allocates buffers in conventional memory.  So you don't have to worry
> about that.  (Only conventional memory buffers can have a real-mode
> segment, btw.)

I am very confused cause function is returning segments like 1FC2 and i need
to pass physical address to a chip, so what is the physical addres of a
segment like this??