From: Eli Zaretskii <eliz@gnu.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Support for Xilinx MicroBlaze architecture (1 of 3)
Date: Sat, 12 Sep 2009 08:47:00 -0000 [thread overview]
Message-ID: <833a6s1rds.fsf@gnu.org> (raw)
In-Reply-To: <4AAAA1CF.6080403@eagercon.com>
> Date: Fri, 11 Sep 2009 12:15:27 -0700
> From: Michael Eager <eager@eagercon.com>
>
> The attached patch adds support for the Xilinx MicroBlaze architecture.
Thanks.
I have a few comments for the documentation part of the patch:
> By default
> +@code{xmd} uses port @code{1234}.
Is there a way to change this default, and if so, should we let the
user know how to do that?
> +@item target remote XMD-HOST:1234
> +@kindex target remote xmd-host>:1234
> +Use this command to connect to the target if you are running @value{GDBN}
> +on a different system @code{xmd}, which is running on @code{XMD-HOST}.
I understand that XMD-HOST stands for the real name of the host. If
so, we use the @var markup in Texinfo for this:
+@item target remote @var{xmd-host}:1234
+Use this command to connect to the target if you are running @value{GDBN}
+on a different system @code{xmd}, which is running on @var{xmd-host}.
Finally, the index entries you have are not useful: they all are for
commands that are not specific to the XMD target, and already have
index entries elsewhere in the manual, where the general form of these
commands is described. What is needed in this section is @cindex
entries about the XMD itself, so that the reader could easily find
this section. So I suggest these entries immediately after the
@subsection line:
@cindex Xilinx MicroBlaze
@cindex XMD, Xilinx Microprocessor Debugger
Okay with these changes.
next prev parent reply other threads:[~2009-09-12 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 19:15 Michael Eager
2009-09-12 8:47 ` Eli Zaretskii [this message]
2009-09-12 18:35 ` Michael Eager
2009-09-12 19:36 ` Eli Zaretskii
2009-09-12 8:49 ` Eli Zaretskii
2009-09-12 18:36 ` Michael Eager
2009-09-14 17:04 ` Joel Brobecker
2009-09-14 17:29 ` Michael Eager
2009-09-14 17:34 ` Joel Brobecker
2009-09-14 17:39 ` Michael Eager
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=833a6s1rds.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox