|
From: | al so |
Subject: | Re: [lwip-users] uIP alternatives |
Date: | Mon, 14 Sep 2020 11:55:52 -0700 |
_______________________________________________I won't be a lot of help here, but I converted from uIP to lwIP many years ago. They are totally different beasts. uIP is extremely simple and limited with only one packet buffer. The amount of RAM used by lwIP is really up to you depending on how you configure it.I'll never use uIP for anything again if I can help it. It's really only good for simple connected sensors. Using it to display even an extremely simple text web page is a challenge to say the least.On Tuesday, September 8, 2020, 01:52:55 AM CDT, Andrew Pullin <pullin@berkeley.edu> wrote:If someone could get smoltcp stood up on bare metal embedded, that could be an option:
https://github.com/smoltcp-rs/smoltcp
On 9/7/20 11:48 PM, al so wrote:
Are there more lightweight FOSS tcp/ip stacks you are aware of?
On Fri, Sep 4, 2020 at 1:58 PM al so <volkswak@gmail.com> wrote:
Given uIP stack doesn't seem to be actively maintained(no activity last 8 years), Is lwip a viable secure alternative?
If true, what is the typical migration effort to replace uIP with lwip.How does lwip compare with uIP in terms of resource utilization (memory/cpu)?
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
[Prev in Thread] | Current Thread | [Next in Thread] |