X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=doc%2Fld65.sgml;h=2195ca48daa4d05183b0ebc3870b89f2b75ffd1a;hb=1a5fa6dc512221490c5547505668a78308f904a8;hp=0230b517fbc4969c148b91e44ef9672bd7aefe35;hpb=b9ea77b18588d24a8bc84f10db7c73f5fceca4f5;p=cc65

diff --git a/doc/ld65.sgml b/doc/ld65.sgml
index 0230b517f..2195ca48d 100644
--- a/doc/ld65.sgml
+++ b/doc/ld65.sgml
@@ -24,21 +24,21 @@ It complements the features that are built into the ca65 macroassembler:
 
 <itemize>
 
-<item>	Accept any number of segments to form an executable module.
+<item>  Accept any number of segments to form an executable module.
 
-<item>	Resolve arbitrary expressions stored in the object files.
+<item>  Resolve arbitrary expressions stored in the object files.
 
-<item>	In case of errors, use the meta information stored in the object files
-	to produce helpful error messages. In case of undefined symbols,
-	expression range errors, or symbol type mismatches, ld65 is able to
-	tell you the exact location in the original assembler source, where
-	the symbol was referenced.
+<item>  In case of errors, use the meta information stored in the object files
+        to produce helpful error messages. In case of undefined symbols,
+        expression range errors, or symbol type mismatches, ld65 is able to
+        tell you the exact location in the original assembler source, where
+        the symbol was referenced.
 
-<item>	Flexible output. The output of ld65 is highly configurable by a config
-	file. Some more-common platforms are supported by default configurations
-	that may be activated by naming the target system. The output
-	generation was designed with different output formats in mind, so
-	adding other formats shouldn't be a great problem.
+<item>  Flexible output. The output of ld65 is highly configurable by a config
+        file. Some more-common platforms are supported by default configurations
+        that may be activated by naming the target system. The output
+        generation was designed with different output formats in mind, so
+        adding other formats shouldn't be a great problem.
 
 </itemize>
 
@@ -808,8 +808,7 @@ segment.
 <sect1>Other SEGMENT attributes<p>
 
 Segments may be aligned to some memory boundary. Specify "<tt/align = num/" to
-request this feature. Num must be a power of two. To align all segments on a
-page boundary, use
+request this feature. To align all segments on a page boundary, use
 
 <tscreen><verb>
         SEGMENTS {
@@ -938,9 +937,24 @@ has several attributes that may be defined here.
     }
 </verb></tscreen>
 
-The Atari file format has only one attribute, <tt/RUNAD/ that allows to specify
-a symbol as the run address of the binary. If the attribute is omiteed, no run
-address is specified.
+The Atari file format has two attributes:
+
+<descrip>
+
+  <tag><tt>RUNAD = symbol</tt></tag>
+
+  Specify a symbol as the run address of the binary, the loader will call this
+  address after all the file is loaded in memory. If the attribute is omitted,
+  no run address is included in the file.
+
+  <tag><tt>INITAD = memory_area : symbol</tt></tag>
+
+  Specify a symbol as the initialization address for the given memory area.
+  The binary loader will call this address just after the memory area is loaded
+  into memory, before continuing loading the rest of the file.
+
+</descrip>
+
 
 <tscreen><verb>
     FORMATS {
@@ -1148,14 +1162,14 @@ including commercial applications, and to alter it and redistribute it
 freely, subject to the following restrictions:
 
 <enum>
-<item> 	The origin of this software must not be misrepresented; you must not
-       	claim that you wrote the original software. If you use this software
-       	in a product, an acknowledgment in the product documentation would be
-	appreciated but is not required.
-<item>	Altered source versions must be plainly marked as such, and must not
-	be misrepresented as being the original software.
-<item>	This notice may not be removed or altered from any source
-	distribution.
+<item>  The origin of this software must not be misrepresented; you must not
+        claim that you wrote the original software. If you use this software
+        in a product, an acknowledgment in the product documentation would be
+        appreciated but is not required.
+<item>  Altered source versions must be plainly marked as such, and must not
+        be misrepresented as being the original software.
+<item>  This notice may not be removed or altered from any source
+        distribution.
 </enum>