uIP

[Trev]

I ported uIP to MS-DOS (using the PC/TCP Packet Driver Specification), and I was wondering if there's any interest in seeing uIP ported to Amiga OS on top of SANA-II? The initial port would be simple--uIP is intended to be embedded in the application--but I don't think it would be difficult to put it in a library with the eventual goal of bsdsocket compatibility.

In my DOS implementation, which is essentially a quick port of the UNIX sample, performance is primarily driven by how often the application loops and calls uIP's periodic bits. lwIP is probably a better choice for a general purpose stack, but porting uIP is a snap and the lessons learned from building a bsdsocket compatibility layer can be applied to future lwIP work.

Thoughts? Folks have mentioned porting uIP and/or lwIP to Amiga before, but I haven't seen any code.

Trev

[Trev]

@weirdami

Yeah, I do a bit of DOS hacking. I've spent quite a bit of time sorting out DOS file system interfaces and correcting bits that Undocumented DOS and other sources have got wrong. It's good fun. The impetus was a previous employer's deision to disable LAN Manager authentication throughout the corporation. Obviously, that limits what you can do with Microsoft's DOS network clients, and I started thinking about a replacment. Anyhow, I don't have anything solid sitting around. Just lots of notes, disassembled software, and C and assembly toys.

@all

uIP is designed for extremely resource limited systems, but it's not really intended to be a general purpose stack. Still, it's used in lots of place, and it's fun to work with. I'll be cleaning up and towering my Amiga mess over the next couple weeks. Sounds like uIP will be project number one.

Trev

[Trev]

So the uIP port is done, but it needs to be properly tested and debugged. I also need to add some command-line options. Wouldn't be too useful as a demonstration if it only worked on one device. ;-) Anyhow, my proper Amiga is still waiting for a few parts. I'm thinking Thursday or Friday for delivery, so I should be able to finish up next weekend. My birthday is next week, though, so it may be tough to fit everything in. Anyhow, soon, but hopefully not in the Amiga, Inc. sense of the word. :-P

Trev

[Trev]

gcc (as compiled by/distributed with AmiDevCpp) is compiling the code in such a why that changes to global variables are not visible cross-module. Optimization is disabled, and volatile doesn't work regardless. Still, I can hack it into working by accessing the variable in some other way--printf for example. This all points to a volatile-like issue, but I haven't looked at a listing yet. Anyhow, ARP and ICMP work.

It's my view that cross-platform code should stay cross-platform, so I'm attempting to stay out of the uIP code itself unless its necessary to fix an IP-related issue. I'd also like to be able to just drop in future uIP releases with minimal changes to Amiga-specific code.

If all goes well, I'll have a little demo ready tonight. As I've said, uIP is not a general purpose stack, but it could be used an embedded or fallback stack for small applcations, e.g. Amiga Explorer. (Note that Cloanto would have to modify Amiga Explorer for that to work.) Still, wrapping a bsdsocket.library interface around uIP is possible.

Anyhow, onto lwIP after this.

Trev