From: ol.sc <ol.sc@b7a2c559-68d2-44c3-8de9-860c34a00d81>
Date: Wed, 30 Sep 2009 21:54:20 +0000 (+0000)
Subject: Updated doc to better reflect current code.
X-Git-Tag: V2.13.0rc2~5
X-Git-Url: https://git.sur5r.net/?p=cc65;a=commitdiff_plain;h=ce778c4bb8315f03f4aa25c6823b1db90f1e67b0;hp=9ba5252a01703566565f817278c023fe2a4134f3

Updated doc to better reflect current code.

git-svn-id: svn://svn.cc65.org/cc65/trunk@4283 b7a2c559-68d2-44c3-8de9-860c34a00d81
---

diff --git a/doc/ld65.sgml b/doc/ld65.sgml
index 5e9a777ef..4afaef5c7 100644
--- a/doc/ld65.sgml
+++ b/doc/ld65.sgml
@@ -950,15 +950,22 @@ __STACKSIZE__=xxx/ on the command line.
 
 <sect1>Builtin configurations<p>
 
-The builtin configurations are part of the linker source. They are also
-distributed together with the machine specific binary packages (usually in the
-doc directory) and don't have a special format. So if you need a special
-configuration, it's a good idea to start with the builtin configuration for
-your system. In a first step, just replace <tt/-t target/ by <tt/-C
+The builtin configurations are part of the linker source. They can be retrieved
+with <tt/--dump-config/ and don't have a special format. So if you need a
+special configuration, it's a good idea to start with the builtin configuration
+for your system. In a first step, just replace <tt/-t target/ by <tt/-C
 configfile/. Then go on and modify the config file to suit your needs.
 
 
 
+<sect1>Secondary configurations<p>
+
+Several machine specific binary packages are distributed together with secondary
+configurations (in the cfg directory). These configurations can be used with
+<tt/-C configfile/ too.
+
+
+
 <sect>Special segments<p>
 
 The builtin config files do contain segments that have a special meaning for
@@ -983,10 +990,11 @@ This segment contains the startup code which initializes the C software stack
 and the libraries. It is placed in its own segment because it needs to be
 loaded at the lowest possible program address on several platforms.
 
-<sect1>HEAP<p>
+<sect1>ZPSAVE<p>
 
-This segment defines the location of the memory heap used by the malloc
-routine.
+The ZPSAVE segment contains the original values of the zeropage locations used
+by the ZEROPAGE segment. It is placed in its own segment because it must not be
+initialized.