X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
	s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
	mime-version; bh=RSZZwFiHgvzmyDPlYmMGtNesNoMBzPgOVbN5tC1ps3c=; b=UKyTPX73k10w
	hnxFRCqYMbQG4epxROhqPQ5mgsbdtdzMGQDKDLBW7Ai4IYRnmCwl0y4qhdJHuB6B+vGoA6ZGhBXqE
	qChAOPnvRQ7Fov8RGZebhm7FpDSf/o3nnqgQk3F3jzVhHYvkGkQmCPldIOHrTM2U1oSNLm7L163gS
	BaReLrsniKGYusj9CrhIUyJC/vN3lUSkVb+WJ0LLxxyVBdFpHn35wdU+BOR/cd6E58oIZKSalLyvR
	+8tCue/IOLnDR60eaoPdehQWX6A312tkXRvcEabNFlvRfyyagkYvP1N5TR/9Kty5RZ+M5kaZwoLNA
	j+ZAjnl3yXE8loulK982Cw==;
Date:	Sun, 25 Feb 2024 14:56:07 +0200
Message-Id:	<86wmqswvmg.fsf@gnu.org>
From:	"Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To:	Pali <pali AT pali DOT im>
Cc:	djgpp AT delorie DOT com
In-Reply-To:	<20240225124223.qq46f2jz7hj3gduv@pali> (message from Pali on Sun,
	25 Feb 2024 13:42:23 +0100)
Subject:	Re: DJGPP documentation updates
References:	<20240213210641 DOT 52jnxonf3zuc2qxw AT pali>
	<CAA2C=vA9F0qL8vAw+FA5AtVavsEZqJKY=UrMz8MbpQa1POqjLA AT mail DOT gmail DOT com>
	<86mss3xfu9 DOT fsf AT gnu DOT org>
	<20240217155210 DOT cs5mqv3izh5jlvee AT pali>
	<86eddbt6e3 DOT fsf AT gnu DOT org> <20240225124223 DOT qq46f2jz7hj3gduv AT pali>
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

> Date: Sun, 25 Feb 2024 13:42:23 +0100
> From: Pali <pali AT pali DOT im>
> Cc: djgpp AT delorie DOT com
> 
> Hello, the next documentation change is for __djgpp_map_physical_memory()
> function. Document requirements / restrictions for out_addr/num_bytes
> parameters and extend example how to use this function. I think that the
> full example is useful because without it I had to read djgpp source
> code to understand what kind of pointer I can pass for out_addr. If you
> like this change, feel free to reformat or rephrase new description.
> 
> --- src/libc/dpmi/helper/mapmem.txh
> +++ src/libc/dpmi/helper/mapmem.txh
> @@ -21,6 +21,22 @@ be set to @code{EINVAL} and the routine will fail.
>  This routine properly handles memory ranges that span multiple DPMI
>  handles, while @code{__dpmi_map_device_in_memory_block} does not.
>  
> +Every page in the specified address range @var{out_addr}, @var{num_bytes}
> +must belong to some DPMI handle in @code{__djgpp_memory_handle_list}
> +allocated by @code{sbrk()}.

Please specify function by their name alone, as in @code{sbrk},
without the parentheses.  "sbrk()" looks like a call to 'sbrk' with no
arguments, which is not what you mean here.  Same with references to
other functions in the patch.  (I realize that the fashion of
referencing functions by using the parentheses exists out there in
other projects, but we don't follow it here.)

Thanks.

- Raw text -