Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rfa] [2/4] SPU enhancements: main part
Date: Sat, 02 Jun 2007 20:21:00 -0000	[thread overview]
Message-ID: <ufy5a2jln.fsf@gnu.org> (raw)
In-Reply-To: <200706021932.l52JW0D7005267@d12av02.megacenter.de.ibm.com> 	(uweigand@de.ibm.com)

> Date: Sat, 2 Jun 2007 21:32:00 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: eliz@gnu.org
> 
> Eli, are the doc changes OK?

Yes, but please fix the following gotcha:

> +@table @code
> +@item info spu event
> +@kindex info spu event
> +Display SPU event facility status.  Shows current event mask
> +and pending event status.
> +
> +@item info spu signal
> +@kindex info spu signal
> +Display SPU signal notification facility status.  Shows pending
> +signal-control word and signal notification mode of both signal
> +notification channels.
> +
> +@item info spu mailbox
> +@kindex info spu mailbox
> +Display SPU mailbox facility status.  Shows all pending entries,
> +in order of processing, in each of the SPU Write Outbound,
> +SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes.
> +
> +@item info spu dma
> +@kindex info spu dma
> +Display MFC DMA status.  Shows all pending commands in the MFC
> +DMA queue.  For each entry, opcode, tag, class IDs, effective
> +and local store addresses and transfer size are shown.
> +
> +@item info spu proxydma
> +@kindex info spu proxydma

It is not useful to have so many index entries that all begin with
"info spu" and all point to almost the same place (probably the same
page in the printed manual).  It is better to have just one index
entry "info spu".


  reply	other threads:[~2007-06-02 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 19:32 Ulrich Weigand
2007-06-02 20:21 ` Eli Zaretskii [this message]
2007-06-03 13:22   ` Ulrich Weigand
2007-06-03 13:32     ` Eli Zaretskii
2007-06-04 19:36 ` Daniel Jacobowitz
2007-06-12 14:41 ` Ulrich Weigand

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=ufy5a2jln.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.com \
    /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