[Coco] DriveWire 3.0 Candidate Specification is now online

[Boisy Pitre]

Hey John,

For NitrOS-9, breakpoints are done by inserting the SWI 1-byte opcode  
into the execution path.  The SWI vector then routes executino into  
the wirebug debugging memory module loaded as part of bootup.  That  
module is responsible for talking to the DriveWire server.

For DECB, there's nothing running at the moment.

Boisy

On Feb 10, 2009, at 9:34 AM, John W. Linville wrote:

> On Tue, Feb 10, 2009 at 09:19:44AM -0600, Boisy Pitre wrote:
>
>> I have posted a document entitled "DriveWire Protocol Version 3.0
>> Candidate Specification" on our website at http://www.cloud9tech.com/
>> Click on the "Support" tab, then scroll all the way down to the  
>> bottom
>> of the Support page, and you will find the link to this document at  
>> the
>> lower right hand side. I am looking for feedback on this document,  
>> and
>> especially interested in comments about the WireBug protocol, which
>> defines a standard for remote debugging.
>
> Looks cool.  How do you do breakpoints?
>
> John
> -- 
> John W. Linville		Someday the world will need a hero, and you
> linville at tuxdriver.com			might be all we have.  Be ready.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com