[Coco] Source code for High Speed Bit-Banger I/O

[coco at yourdvd.net]

Okay, now that's the first laugh I've had in days....


> -------- Original Message --------

> Subject: Re: [Coco] Source code for High Speed Bit-Banger I/O

> From: David Roper <dave at ebonhost.com>

> Date: Fri, April 27, 2007 2:33 am

> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>

> 

> I detect an element of my "9-pin male plug is larger than your 9-pin 

> male plug" going on here...

> 

> Kind Regards,

> 

> David Roper

> 

> -------------------------------------------------------------------------

> *My Graphic Garden / Ebonhost*

> *website:* www.mygraphicgarden.com.au

> *phone:* (02) 4268 5934

> *fax:* (02) 4268 6456

> *mail:* po box 624 thirroul, nsw 2515

> *email:* dave at ebonhost.com

> -------------------------------------------------------------------------

> *Legal: The information contained in this email communication, and any 

> attachments, is confidential.

> Please don't distribute, copy or quote. If you have received this 

> communication in error, please notify

> customerservice at mygraphicgarden.com.au immediately.*

> 

> 

> Roger Taylor wrote:

> > At 07:42 PM 4/26/2007, you wrote:

> > The speed increase, interleaved checksum, framing error detection, 

> > variable request count and termination due to a pause in the 

> > transmission were all my own enhancements.

> >

> >> I tested both the 57600 and the 115.2K operation on a CoCo 3 

> >> connected to my PowerMac G4 through a KeySpan High-Speed Serial 

> >> adapter and the serial cable I bought from you. All my tests worked 

> >> flawlessly (I have transferred whole disk images both ways without 

> >> any data corruption).

> >>

> >> Darren

> >

> >

> > Good job, then.  If it works, then I guess I can't claim to be the 

> > only one who made it possible.  :)

> >

> > Now, my own 115.2k model definately uses some strikingly similar areas 

> > of the code you posted, but then I adapted it from the comm source as 

> > well.  The 16,15,16,15,16,15,16,15 cycle timing is really the only way 

> > to do it for syncing the received bits, so that part is a given no 

> > matter how you code it.  :)

> >

> > However, my model and protocol was designed to work in a 

> > background-driven environment.  The CoCo can literally sit there with 

> > a flashing cursor and talk to a PC at 115200 bps with nothing missed!  

> > This is on a CoCo 1, 2, or 3 and no GIME or IRQ/FIRQ involved!  What 

> > about a PC running at 3ghz and well enough capable of transmitting too 

> > quick while the CoCo is possibly executing a slow 1 or 2mhz 

> > instruction.  Solved!  :)

> >

> >

> >

> >

> 

> --

> Coco mailing list

> Coco at maltedmedia.com

> http://five.pairlist.net/mailman/listinfo/coco