From: Johan Rydberg <jrydberg@rtmk.org>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Johan Rydberg <jrydberg@rtmk.org>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] remote_rcmd
Date: Mon, 15 Jul 2002 11:49:00 -0000 [thread overview]
Message-ID: <20020715204119.G14830@cockmaster.bredbandsbolaget.se> (raw)
In-Reply-To: <3D31C2DF.3000708@ges.redhat.com>; from ac131313@ges.redhat.com on Sun, Jul 14, 2002 at 20:28:47 +0200
On 2002.07.14 20:28 Andrew Cagney wrote:
: > I think I wasn't clear in my question. qRcmd can send some O packets,
: > which are supposed to provide some ambiguous form of "output" from the
: > "console", and then one <HEX-OUTPUT> packet. What is supposed to go in
: > which? It doesn't make sense to me to limit this to one <HEX-OUTPUT>
: > packet if it is arbitrary output; it may simply be too large. On the
: > other hand I'm not sure I see why both O<HEX> and <HEX> are allowed.
If I'm not mistaken, the "O"-packet is used for just transfering one
character, not a string.
: Sorry, you've lost me. There are a number of choices and which is used
: is left to the implementor. Sequences like:
:
: <- O output
: <- O output
: <- OK
: and
: <- O output
: <- output
: and
: <- output
: and
: <- OK
:
: are all valid. To be honest, I've only seen targets use the last two.
: Typically the command response is so small that it can be safely
: squeesed into a single reply packet.
Typically it can squeese into one packet, yes. But should the protocol
really put a limit on the output?
regards
johan
next prev parent reply other threads:[~2002-07-15 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020627035114.M1899@cockmaster.bredbandsbolaget.se>
2002-07-14 9:51 ` Andrew Cagney
2002-07-14 10:48 ` Daniel Jacobowitz
2002-07-14 11:00 ` Andrew Cagney
2002-07-14 11:01 ` Daniel Jacobowitz
2002-07-14 17:53 ` Andrew Cagney
2002-07-15 11:49 ` Johan Rydberg [this message]
2002-07-15 13:02 ` Andrew Cagney
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=20020715204119.G14830@cockmaster.bredbandsbolaget.se \
--to=jrydberg@rtmk.org \
--cc=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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