I can comment on the ESP8266 side.
It does not use 1.4.1 nor 2.0.3 but a custom (heavily modified) git head
grabbed some time between 1.4.1 and 2.0 when there was a probable 1.5 to
come, as that is what they advertise on their VERSION strings.
They have their own sort-of-OS taking care of all the WiFi stuff and
providing some non-WiFi-used CPU time to the rest of the "tasks", which
must use their custom C library functions.
But I guess you know quite better than me on this very subject, so my
former comment is probably useless for you and just for the rest of the
readers.
AFAIK, pbufs are single (non-chained) on the Tx side and probably
multiple (chained) on the Rx side, depending on the memory allocation
strategy, which serves the purpose of avoiding memory fragmentation
issues. Maybe there's something I'm missing, but I think probably your
needs are more on the alloc world and not TCP/IP functions related ?
Off-topic: I gave up with that chip, I'm currently fighting the ESP32.
Though it still uses this custom lwIP fork, it has JTAG...
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
