Re: Merging OC gdb with official gdb

[Marko Mlinar <markom@opencores.org>]

> How is your texinfo?
here:

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.124
diff -c -3 -p -r1.124 gdb.texinfo
*** gdb.texinfo 21 Sep 2002 00:29:04 -0000      1.124
--- gdb.texinfo 23 Sep 2002 11:44:10 -0000
*************** Michael Tiemann contributed SPARC suppor
*** 394,399 ****
--- 394,400 ----
  Tim Tucker contributed support for the Gould NP1 and Gould Powernode.
  Pace Willison contributed Intel 386 support.
  Jay Vosburgh contributed Symmetry support.
+ Marko Mlinar contributed OpenRISC 1000 support.

  Andreas Schwab contributed M68K Linux support.

*************** The timeout set by @code{set timeout} do
*** 12236,12241 ****
--- 12237,12343 ----
  is waiting for your program to stop.  In that case, @value{GDBN} waits
  forever because it has no way of knowing how long the program is going
  to run before stopping.
+ @end table
+
+ @node OpenRISC 1000
+ @subsection OpenRISC 1000
+
+ @cindex or1k boards
+ See OR1k Architecture document (@url{www.opencores.org}) for more 
information
+ about platform and commands.
+
+ @table @code
+
+ @kindex target jtag
+ @item target jtag jtag://@var{host}:@var{port}
+
+ Connects to remote JTAG server.
+ JTAG remote server can be either an or1ksim or JTAG server,
+ connected via parallel port to the board.
+
+ Example: @code{target jtag jtag://localhost:9999}
+
+ @kindex or1ksim
+ @item or1ksim @var{command}
+ If connected to @code{or1ksim} OpenRISC 1000 Architectural
+ Simulator, proprietary commands can be executed.
+
+ @kindex info or1k spr
+ @item info or1k spr
+ Displays spr groups.
+
+ @item info or1k spr @var{group}
+ @item info or1k spr @var{groupno}
+ Displays register names in selected group.
+
+ @item info or1k spr @var{group} @var{register}
+ @item info or1k spr @var{register}
+ @item info or1k spr @var{groupno} @var{registerno}
+ @item info or1k spr @var{registerno}
+ Shows information about specified spr register.
+
+ @kindex spr
+ @item spr @var{group} @var{register} @var{value}
+ @item spr @var{register @var{value}}
+ @item spr @var{groupno} @var{registerno @var{value}}
+ @item spr @var{registerno @var{value}}
+ Writes @var{value} to specified spr register.
+
+ @kindex hwatch
+ @item hwatch @var{conditional}
+ Set hardware watchpoint on combination of Load/Store Effecive Address(es)
+ or Data.  For example:
+
+ @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && 
($SDATA >= 50)}
+
+ @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && 
($SDATA >= 50)}
+
+ @kindex htrace info
+ @item htrace info
+ Display information about current HW trace configuration.
+
+ @kindex htrace trigger
+ @item htrace trigger @var{conditional}
+ Set starting criteria for HW trace.
+
+ @kindex htrace qualifier
+ @item htrace qualifier @var{conditional}
+ Set acquisition qualifier for HW trace.
+
+ @kindex htrace stop
+ @item htrace stop @var{conditional}
+ Set HW trace stopping criteria.
+
+ @kindex htrace record
+ @item htrace record @var{[data]*}
+ Selects the data to be recorded, when qualifier is met and HW trace was
+ triggered.
+
+ @kindex htrace enable
+ @item htrace enable
+ @kindex htrace disable
+ @item htrace disable
+ Enables/disables the HW trace.
+
+ @kindex htrace rewind
+ @item htrace rewind @var{[filename]}
+ Clears currently recorded trace data.
+
+ If filename is specified, new trace file is made and any newly collected 
data
+ will be written there.
+
+ @kindex htrace print
+ @item htrace print @var{[start [len]]}
+ Prints trace buffer, using current record configuration.
+
+ @kindex htrace mode continuous
+ @item htrace mode continuous
+ Set continuous trace mode.
+
+ @kindex htrace mode suspend
+ @item htrace mode suspend
+ Set suspend trace mode.
+
  @end table

  @node PowerPC