Tue Mar 29 22:38:45 EDT 2011

Packet-based monitor code

I'm not sure if that's going to work directly with the current
implementation.  Maybe best to move the current serial port approach
to a packet API.


in/b and friends seem to be only called in `target-recieve+id/b' and
`target-count'.  The latter is an artifact of the daisy-chain serial
and needs to move to a different level.  The former already hints at a
message-based approach.

Basically, we can buffer up to the point that we read.  This means the
byte-oriented "printf" style can be maintained as it works quite well.

Looks like all commands expect a reply except for reset.