Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: drow@false.org, schwab@suse.de, gdb-patches@sources.redhat.com
Subject: Re: ColdFire/fido support
Date: Sat, 16 Jun 2007 10:21:00 -0000	[thread overview]
Message-ID: <u7iq4i4je.fsf@gnu.org> (raw)
In-Reply-To: <200706152305.25699.vladimir@codesourcery.com> (message from 	Vladimir Prus on Fri, 15 Jun 2007 23:05:25 +0400)

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Fri, 15 Jun 2007 23:05:25 +0400
> Cc: Andreas Schwab <schwab@suse.de>,  gdb-patches@sources.redhat.com,  Eli Zaretskii <eliz@gnu.org>
> 
> Does this doco patch look good?

It's okay, but I'd prefer to convert the two subsections--the old ARM
one and the new one you wrote--into @node's, and add a menu in their
parent.  With two targets (and more to come, I presume), it is no
longer a good idea to hide those subsections from the menu traversing
commands of an Info reader.

> +An M68K target is required to have either the
> +@samp{org.gnu.gdb.m68k.core} feature or the
> +@samp{org.gnu.gdb.coldfire.core} feature or the 
> +@samp{org.gnu.gdb.fido.core} feature.  Which feature is present
> +determines which flavour of m68k is used.  The present feature 
> +should contain registers @samp{d0} through @samp{d7}, 
> +@samp{a0} through @samp{a5}, @samp{fp}, @samp{sp}, @samp{ps} and 
> +@samp{pc}.
> +
> +The @samp{org.gnu.gdb.coldfire.fp} feature is optional.  If present, it
> +should contain registers @samp{fp0} through @samp{fp7},
> +@samp{fpcontrol}, @samp{fpstatus} and @samp{fpiaddr}.

Isn't it better to use an @itemize list here?  How about the following
rewording:

    @node M68K Features
    @subsection M68K Features
    @cindex target descriptions, M68K features

    An M68K target can have either one of the following features:
    @itemize @bullet{}
    @item
    @samp{org.gnu.gdb.m68k.core}
    @itemx
    @samp{org.gnu.gdb.coldfire.core}
    @itemx
    @samp{org.gnu.gdb.fido.core}
    The feature that is present determines which flavor of m86k is
    used.  The feature that is present should contain registers
    @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp},
    @samp{sp}, @samp{ps} and @samp{pc}.

    @item
    @samp{org.gnu.gdb.coldfire.fp}
    This feature is optional.  If present, it should contain registers
    @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and
    @samp{fpiaddr}.
    @end itemize

Finally, please use the US English variant of spelling: "flavor", not
"flavour".


  reply	other threads:[~2007-06-16 10:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  9:37 Vladimir Prus
2007-05-05 11:02 ` Andreas Schwab
2007-05-06 11:52   ` Vladimir Prus
2007-05-28 11:43     ` Vladimir Prus
2007-06-05 15:19       ` Daniel Jacobowitz
2007-06-08 10:58         ` Vladimir Prus
2007-06-12 13:38           ` Daniel Jacobowitz
2007-06-15 10:17             ` Vladimir Prus
2007-06-15 14:47               ` Daniel Jacobowitz
2007-06-15 19:05                 ` Vladimir Prus
2007-06-16 10:21                   ` Eli Zaretskii [this message]
2007-06-19 16:39                     ` Vladimir Prus
2007-06-19 16:53                       ` Eli Zaretskii
2007-06-19 17:10                         ` Daniel Jacobowitz
2007-06-19 18:00                           ` Eli Zaretskii
2007-06-20  9:14                             ` Vladimir Prus
2007-06-20 18:15                               ` Eli Zaretskii
2007-06-30 15:47       ` Andreas Schwab
2007-06-30 16:00         ` Daniel Jacobowitz

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=u7iq4i4je.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    --cc=vladimir@codesourcery.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