On Sun, Jul 14, 2002 at 01:48:38PM -0400, Andrew Cagney wrote:
>
>Actually, the current docs suggest:
>
>-> qRcmd command
><- O <HEX-OUTPUT>
><- O <HEX-OUTPUT>
><- <HEX-OUTPUT>
><- OK
Where?
COMMAND (hex encoded) is passed to the
local interpreter for execution. Invalid
commands should be reported using the
output string. Before the final result
packet, the target may also respond with
number of intermediate `O'OUTPUT console
output packets.
>which confuses me. What's supposed to differentiate the O <HEX-OUTPUT>
>packets from the final <HEX-OUTPUT> packet (what difference in purpose,
>I mean)?
Valid replies to ``qRcmd'' are:
``OK''
``''
``<HEX-OUTPUT>''
``Enn''
The ``O'' packet is something separate.
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.
Sorry, you've lost me. There are a number of choices and which is used
is left to the implementor. Sequences like: