[Coco] Tcp off-loading on CoCo

[L. Curtis Boyle]

Good to know. The overhead of having to save some registers to service it as an FIRQ should not be much compared to reading the whole packet(s), so not having IRQ should not be much of a concern. (If you were to read each data byte separately on an FIRQ/IRQ trigger… that’s a different matter entirely).

L. Curtis Boyle
curtisboyle at sasktel.net



> On Apr 13, 2017, at 10:44 AM, William Astle <lost at l-w.ca> wrote:
> 
> On 2017-04-13 10:29 AM, L. Curtis Boyle wrote:
>> The cart interrupt might be a better option (it can be IRQ, not just FIRQ, right?), as you can shut that on or off at will. So, if a routine knew that polling would be better for it’s situation, it could shut the IRQ off, and poll. If it preferred an IRQ (to block read a bunch of data after completed packets are in - read it like a disk drive sector), it could do that as well.
> 
> The cart interrupt is hard wired to the FIRQ on the coco1/2 (via PIA1 I believe). On the coco3 it can be routed to IRQ, FIRQ, both, or neither through the GIME.
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>