Drop obsolete MLT references in porting guide

[John Dallaway <john at dallaway dot org dot uk>]

This patch drops the obsolete MLT references in the eCos porting guide.
Checked-in.

John Dallaway
eCos maintainer

Index: ChangeLog
===================================================================
RCS file: /cvs/ecos/ecos/packages/hal/common/current/ChangeLog,v
retrieving revision 1.119
diff -U5 -r1.119 ChangeLog
--- ChangeLog	2 Feb 2009 13:46:08 -0000	1.119
+++ ChangeLog	9 Oct 2010 11:32:36 -0000
@@ -1,5 +1,9 @@
+2010-10-09  John Dallaway  <john@dallaway.org.uk>
+
+	* doc/porting.sgml: Delete references to the memory layout editor.
+
 2009-02-02  Bart Veer  <bartv@ecoscentric.com>
 
 	* cdl/hal.cdl: add CYGBLD_GLOBAL_WARNFLAGS, as part of global
 	compiler flags update.
 
@@ -2340,11 +2344,11 @@
 
 //===========================================================================
 // ####GPLCOPYRIGHTBEGIN####                                                
 // -------------------------------------------                              
 // This file is part of eCos, the Embedded Configurable Operating System.   
-// Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
+// Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2010 Free Software Foundation, Inc.
 //
 // This program is free software; you can redistribute it and/or modify     
 // it under the terms of the GNU General Public License as published by     
 // the Free Software Foundation; either version 2 or (at your option) any   
 // later version.                                                           
Index: doc/porting.sgml
===================================================================
RCS file: /cvs/ecos/ecos/packages/hal/common/current/doc/porting.sgml,v
retrieving revision 1.5
diff -U5 -r1.5 porting.sgml
--- doc/porting.sgml	29 Jan 2009 17:49:13 -0000	1.5
+++ doc/porting.sgml	9 Oct 2010 11:32:39 -0000
@@ -7,11 +7,11 @@
 <!--     eCos common HAL documentation                               -->
 <!--                                                                 -->
 <!-- =============================================================== -->
 <!-- ####ECOSDOCCOPYRIGHTBEGIN####                                       -->
 <!-- ===============================================================     -->
-<!-- Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. -->
+<!-- Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2010 Free Software Foundation, Inc. -->
 <!-- This material may be distributed only subject to the terms          -->
 <!-- and conditions set forth in the Open Publication License, v1.0      -->
 <!-- or later (the latest version is presently available at              -->
 <!-- http://www.opencontent.org/openpub/)                                -->
 <!-- Distribution of the work or derivative of the work in any           -->
@@ -1795,11 +1795,11 @@
 </para>
 
 <orderedlist>
 <listitem><para>Copy an existing platform HAL from the same or another
     architecture. Rename the files as necessary to follow the
-    standard: CDL and MLT related files should contain the
+    standard: CDL and memory layout related files should contain the
     &lt;arch&gt;_&lt;variant&gt;_&lt;platform&gt; triplet.</para>
 </listitem>
 
 <listitem><para>Adjust CDL options. Primarily option naming, real-time
     clock/counter, and CYGHWR_MEMORY_LAYOUT variables, but also other
@@ -1815,16 +1815,16 @@
     linkend="hal-porting-ecos-database">. Initially, the target entry
     should only contain the HAL packages. Other hardware support
     packages will be added later.</para>
 </listitem>
 
-<listitem><para>Adjust the MLT files in
+<listitem><para>Adjust the memory layout files in
     <filename>include/pkgconf</filename> to match the memory layout on
-    the platform. For initial testing it should be enough to just hand
+    the platform. <!-- For initial testing it should be enough to just hand
     edit .h and .ldi files, but eventually you should generate all
     files using the memory layout editor in the configuration
-    tool. See <xref linkend="hal-porting-platform-memory-layout"> for
+    tool. --> See <xref linkend="hal-porting-platform-memory-layout"> for
     more details.</para>
 </listitem>
 
 <listitem>
     <para>
@@ -2589,32 +2589,39 @@
 <!-- {{{ Platform Memory Layout -->
 
 <section id="hal-porting-platform-memory-layout">
 <TITLE>Platform Memory Layout</TITLE>
 
-<para>The platform memory layout is defined using the Memory
-Configuration Window <!-- [FIXME: ref] --> in the Configuration Tool.</para>
+<para>Historically, the platform memory layout was defined using a Memory
+Configuration window in the eCos Configuration Tool (version 1.x).
+However, the memory layout feature was not ported to the wxWidgets version
+of the tool (version 2.0 and later). Memory layouts are currently manipulated
+using a text editor.</para>
 
+<!--
 <note>
 <para>If you do not have access to a Windows machine, you can
 hand edit the <filename>.h</filename> and <filename>.ldi</filename> files to match the
 properties of your platform. If you want to contribute your port back
 to the eCos community, ask someone on the list to make proper memory
 map files for you.</para>
 </note>
+-->
 
 <section>
 <title>Layout Files</title>
 
-<para>The memory configuration details are saved in three files:</para>
+<para>The memory configuration details are specified in two files:</para>
 
 <variablelist>
+<!--
 <varlistentry>
 <term><filename>.mlt</filename></term>
 	<listitem><para>This is the Configuration Tool save-file. It is only used
 	by the Configuration Tool.</para></listitem>
 </varlistentry>	
+-->
 <varlistentry>
 <term><filename>.ldi</filename></term>
 	<listitem><para>This is the linker script fragment. It defines the memory
 	and location of sections by way of macros defined in the
 	architecture or variant linker script.</para></listitem>
@@ -2625,12 +2632,15 @@
 	macros, allowing eCos or the application adapt the memory
 	layout of a specific configuration.</para></listitem>
 </varlistentry>
 </variablelist>
 
-<para>These three files are generated for each startup-type, since the
-memory details usually differ.</para>
+<para>These files are generated for each startup-type, since the
+memory details usually differ. The layout and structure of new files
+should match those of existing memory layout files to allow for the
+introduction of a new memory layout editor in the future.
+</para>
 
 </section>
 
 <section>
 <title>Reserved Regions</title>
@@ -2638,12 +2648,12 @@
 <para>Some areas of the memory space are reserved for specific
 purposes, making room for exception vectors and various tables. RAM
 startup configurations also need to reserve some space at the bottom
 of the memory map for the ROM monitor.</para>
 
-<para>These reserved areas are named with the prefix "reserved_" which is
-handled specially by the Configuration Tool: instead of referring to a
+<para>These reserved areas are named with the prefix "reserved_" <!-- which is
+handled specially by the Configuration Tool: --> instead of referring to a
 linker macro, the start of the area is labeled and a gap left in the
 memory map.</para>
 
 </section>