Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Flash support part 3: documentation
Date: Thu, 17 Aug 2006 08:24:00 -0000	[thread overview]
Message-ID: <20060816203241.GA403@nevyn.them.org> (raw)
In-Reply-To: <200607221640.31522.vladimir@codesourcery.com>

FYI, I looked over this patch again today; except for minor nits below,
it still accurately describes the other two flash patches.  This covers
the usage and protocol sides, and only the bits in the middle have
changed.

On Sat, Jul 22, 2006 at 04:40:31PM +0400, Vladimir Prus wrote:
> +To be able to write into flash memory, @value{GDBN} needs to obtain
> +memory map from the target.  This section describes the format of the
> +memory map.

"obtain a memory map"?

> +<!DOCTYPE memory-map
> +          PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
> +                 "http://sourceware.org/gdb/gdb-memory-map.dtd">

This URL is not yet valid.  Once the flash patches are merged,
let's remember to make it valid; any DTDs should be available from the
GDB web site.  Automatic XML validation tools will use that.

-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2006-08-16 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20  9:43 Vladimir Prus
2006-07-20 19:57 ` Eli Zaretskii
2006-07-21 12:04   ` Vladimir Prus
2006-07-21 15:33     ` Eli Zaretskii
2006-07-22 12:40       ` Vladimir Prus
2006-07-22 14:05         ` Eli Zaretskii
2006-09-20 22:21           ` Daniel Jacobowitz
2006-09-21  3:22             ` Eli Zaretskii
2006-09-21 14:01               ` Daniel Jacobowitz
2006-08-17  8:24         ` Daniel Jacobowitz [this message]

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=20060816203241.GA403@nevyn.them.org \
    --to=drow@false.org \
    --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