[Coco] Fwd: IP packets on my coco

[Brett Gordon]

Eth framing isnt hard. (Esp. If uIP does the arp part.)  Calc'ing a CRC
isnt horrible, just slow.  The first chip you mentioned will automagically
check the CRC on received packets..

And the esp8266, unless reprogrammed, doesnt jibe with multitasking OSs.
It has the same flow control problems that Drivewire has with it's internet
stuff.  It will work fine to tunnel IP packets to a fixed up dw server,
though. ;)

Brett M Gordon
On Jun 7, 2016 8:33 PM, "RETRO Innovations" <go4retro at go4retro.com> wrote:

> On 6/7/2016 5:56 PM, Brett Gordon wrote:
>
>> Hah...answered my own question..these chips take layer 2 ethernet
>> frames...
>> not too horrible to program for but....computing the CRC in the coco is
>> slow and painfull.  Does one of these chips do the for us?
>>
> Oh, and...
>
> No, they do not. You are responsible for all Ethernet frame creation and
> decoding.
>
> That's what makes the esp8266 more appealing.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>