Re: [PATCH] remote_rcmd

[Daniel Jacobowitz <drow@mvista.com>]

On Sun, Jul 14, 2002 at 12:31:31PM -0400, Andrew Cagney wrote:
> >Hi,
> >
> >This small patch adds support for receving more that ~200 bytes
> >of output from the "qRcmd" request (ie the monitor command).
> >
> >I have no idea if this will break any stubs, but hopefully not.
> >I don't know how often stubs implement the qRcmd request.
> >
> >2002-06-27  Johan Rydberg  <jrydberg@rtmk.org>
> >
> >        * remote.c (remote_rcmd): Continue reading output from
> >        stub until receiving OK.
> 
> If I understand this patch correctly, it is changing things so that it 
> allows:
> 
> 	-> rCmd <command>
> 	<- <HEX-OUTPUT>
> 	<- <HEX-OUTPUT>
> 	<- OK
> 
> This is wrong.  The target should send:
> 
> 	-> rCmd <command>
> 	<- O <HEX-OUTPUT>
> 	<- O <HEX-OUTPUT>
> 	<- OK
> 
> when transfering a longer buffer.

Actually, the current docs suggest:

-> qRcmd command
<- O <HEX-OUTPUT>
<- O <HEX-OUTPUT>
<- <HEX-OUTPUT>
<- OK

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)?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer