[Coco] Serial to Ethernet

[Aaron Wolfe]

On Tue, Feb 10, 2015 at 8:23 PM, Allen Huffman <alsplace at pobox.com> wrote:
>> On Feb 10, 2015, at 2:40 PM, Aaron Wolfe <aawolfe at gmail.com> wrote:
>>
>> Everything I added to DW (networking, etc) was in hopes we could start
>> making software now for hardware that would come in "the future".  Ideally
>> you could just change drivers and a program that does Internet stuff via
>> Drivewire would do Internet stuff via some hardware solution without
>> changes.  Unfortunately since I had no idea what that hardware might look
>> like or how it would work, I had to guess a lot.  If the wiznet chips had
>> existed then, I would have cloned their API.  I did implement one not very
>> different, and also a Hayes AT command API, but it's different enough that
>> software would be best redone specifically for the wiznet.  OTOH we still
>> don't have any hardware and there's very little software using the DW APIs
>> so not a huge deal in any case.
>
> I’ll be getting right on this, soon, Aaron! Is there a tutorial or tech reference on how to write networking modules using /N and such? I can make sure my code matches your existing API.
>

Check out lib/net.a in the nitros9 source for the current network
library.  It only handles TCP connections, no UDP or lower level
functionality (since drivewire uses the host's network stack, it
wasn't needed).  If that isn't suitable for your project, we can come
up with something else.

I think it would be in everyone's interest if all the potential
networking solutions for the coco share a common API so that client
software doesn't have to be redone.  Although DriveWire has such an
API, it's not necessarily the right one to use and I'm more than
willing to adapt to any standard.