[Coco] Tcp off-loading on CoCo

[L. Curtis Boyle]

The using of FIRQ would not be much of a problem on a 6309, since you can tell the CPU to (optionally) push/pull all registers with an FIRQ, or have the normal FIRQ behavior.

L. Curtis Boyle
curtisboyle at sasktel.net



> On Apr 13, 2017, at 12:45 PM, Mark D. Overholser <marko555.os2 at gmail.com> wrote:
> 
> On 13-Apr-17 09:18, Zippster wrote:
>> Because it saves the entire machine state (all register values), like
>> an IRQ, which consumes quite a few cycles.  A FIRQ doesn’t save all
>> the registers and is faster.
>> 
> 
> That means that Code called by a FIRQ needs to Insure that ALL the Registers are like they were when the Interrupt was called..
> 
> 
>> Depending on how your software is written, polling for a status bit
>> to see if data is ready may be faster still, though it doesn’t have
>> the convenience factor of an interrupt.
>> 
> 
> It would depend on How Timely you need to Network Data...
> 
> In a Turned Based Game, your waiting for other players anyway..  In a Real Time Simulation ( or Arcade Game ), you want the Other Player "states" ASAP...