From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Self-describing targets - a more concrete proposal
Date: Wed, 29 Mar 2006 21:49:00 -0000 [thread overview]
Message-ID: <uek0layvp.fsf@gnu.org> (raw)
In-Reply-To: <20060329161624.GA32241@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 29 Mar 2006 11:16:25 -0500)
> Date: Wed, 29 Mar 2006 11:16:25 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> I would appreciate comments on the sample and documentation
Comments on the documentation are below. Note that I needed to guess
what was in the Texinfo source, since you posted the Info output, so I
could have guessed wrong, and my comments might thus be off the target.
> GDB retrieves a target's self-description via the remote protocol using
> a `qPart' request (*note the `qPart' request: qPart request.) of the form:
This cross-reference looks awkward. I'm guessing that Jim used a
2-argument form of a @pxref here. But the second arg is redundant
here because it is a substring of the 1st. Am I missing some valid
reason for using the second argument?
> qPart:features:read:ANNEX:OFFSET,LENGTH
> where ANNEX is the string `target.xml'. The OFFSET and LENGTH
The last line should have a @noindent before it.
> parameters are the offset into the description and the number of bytes
> to transfer, as for other `qPart' requests.
>
> The `target.xml' annex contains an XML document describing the
> target's features; its form is described in *Note Self-Description
> Format::.
There's something I don't understand here: is "target.xml" a literal
fixed string that will _always_ appear in the above packet? If it is,
why do we need to mention its name?
> To reduce protocol overhead, a target may supply a special annex
> named `CHECKSUMS' that provides 160-bit SHA1 checksum values for the
> annexes it has available. The `CHECKSUMS' annex contains a series of
> newline-terminated lines, each of which contains a 40-digit hexidecimal
> checksum, two spaces, and the name of an annex with the given checksum.
> Here is an example `CHECKSUM' annex:
> 68c94ffc34f8ad2d7bfae3f5a6b996409211c1b1 target.xml
> 0e8e850b0580fbaaa0872326cb1b8ad6adda9b0d mmu.xml
> 00f22e5f971ccec05c2acce98caf8cff4343c8cf fpu.xml
Shouldn't we document how to generate a checksum for a file?
Other than that, looks fine to me.
next prev parent reply other threads:[~2006-03-29 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 21:26 Daniel Jacobowitz
2006-03-29 21:49 ` Eli Zaretskii [this message]
2006-03-29 22:27 ` Jim Blandy
2006-03-29 22:32 ` Daniel Jacobowitz
2006-03-29 22:36 ` Rob Nikander
2006-03-29 22:41 ` Paul Koning
2006-03-29 23:38 ` Daniel Jacobowitz
2006-03-30 0:15 ` Joseph S. Myers
2006-03-30 7:11 ` Eli Zaretskii
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=uek0layvp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@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