Re: [PATCH] remote_rcmd

[Andrew Cagney <ac131313 at ges dot redhat dot com>]

> 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.
The ``O'' packet takes 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?
Should it?  Probably not (but it does).

> regards
> johan
Andrew