FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source
This commit is contained in:
Jim Blandy 2001-06-28 23:12:18 +00:00
parent f5e1cf12f7
commit bf93dfed85
2 changed files with 17 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/ChangeLog
View file

@ -1,6 +1,8 @@
2001-06-28 Jim Blandy <jimb@redhat.com> 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_breakpoint_from_pc, d10v_register_byte,
d10v_register_raw_size, d10v_register_virtual_size, d10v_register_raw_size, d10v_register_virtual_size,
d10v_register_virtual_type, d10v_register_convertible, d10v_register_virtual_type, d10v_register_convertible,

15
gdb/d10v-tdep.c
View file

@ -193,7 +193,20 @@ d10v_ts3_register_name (int reg_nr)
return register_names[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 static unsigned long
d10v_ts2_dmap_register (int reg_nr) d10v_ts2_dmap_register (int reg_nr)