* d10v-tdep.c (d10v_ts2_dmap_register): Doc fix.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 923f12fe64b3378e26402f22d38e32ca9e7ed972..73480ebb61d973965c557a799700492420aadde8 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,6 +1,8 @@
 2001-06-28  Jim Blandy  <jimb@redhat.com>
 
-       * d10v-tdep.c (10v_frame_chain_valid, d10v_use_struct_convention,
+       * d10v-tdep.c (d10v_ts2_dmap_register): Doc fix.
+
+       * d10v-tdep.c (d10v_frame_chain_valid, d10v_use_struct_convention,
        d10v_breakpoint_from_pc, d10v_register_byte,
        d10v_register_raw_size, d10v_register_virtual_size,
        d10v_register_virtual_type, d10v_register_convertible,

diff --git a/gdb/d10v-tdep.c b/gdb/d10v-tdep.c
index e41caaf75e247cc781fe25fc5b0a47f8529e111e..f3c0e6fc498d3bdff7dc8d5c04c0cb8c6cf65660 100644 (file)
--- a/gdb/d10v-tdep.c
+++ b/gdb/d10v-tdep.c
@@ -193,7 +193,20 @@ d10v_ts3_register_name (int reg_nr)
   return register_names[reg_nr];
 }
 
-/* Access the DMAP/IMAP registers in a target independent way. */
+/* Access the DMAP/IMAP registers in a target independent way.
+
+   Divide the D10V's 64k data space into four 16k segments:
+   0x0000 -- 0x3fff, 0x4000 -- 0x7fff, 0x8000 -- 0xbfff, and 
+   0xc000 -- 0xffff.
+
+   On the TS2, the first two segments (0x0000 -- 0x3fff, 0x4000 --
+   0x7fff) always map to the on-chip data RAM, and the fourth always
+   maps to I/O space.  The third (0x8000 - 0xbfff) can be mapped into
+   unified memory or instruction memory, under the control of the
+   single DMAP register.
+
+   On the TS3, there are four DMAP registers, each of which controls
+   one of the segments.  */
 
 static unsigned long
 d10v_ts2_dmap_register (int reg_nr)