lwIP 2.1.3 is now available from the lwIP download area on savannah [1]
or via git (using the STABLE-2_1_3_RELEASE tag).
This is again a bugfix-only release on the 2.1.x branch fixing numerous
smaller bugs. For a changelog, see the git log here:
https://git.savannah.nongnu.org/cgit/lwip.git/log/
I'm workikng on a port done by somebody else, and they seem to have
assumed that functions like sys_mbox_set_invalid() don't need to be
thread-safe. But, they did add mutexes to make sure that some other
functions like like sys_mbox_free() and _new() are thread-safe.
The documentation I've found
Am 03.11.2021 um 18:15 schrieb Grant Edwards:
Where do I find the sys_arch.txt and rawapi.txt files that are listed
and described in doc/FILES?
Their content got moved to doxygen documentation back in 2017 which can
be found here:
http://www.nongnu.org/lwip/
However, the doc/FILES file has no
Am 10.11.2021 um 20:43 schrieb Grant Edwards:
I'm workikng on a port done by somebody else, and they seem to have
assumed that functions like sys_mbox_set_invalid() don't need to be
thread-safe. But, they did add mutexes to make sure that some other
functions like like sys_mbox_free() and _new()
Dear lwip devs,
Are there any plans to support mqtt v5 in the near future?
best regards, bas
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
On 2021-11-10, goldsi...@gmx.de wrote:
> Am 10.11.2021 um 20:43 schrieb Grant Edwards:
>> I'm workikng on a port done by somebody else, and they seem to have
>> assumed that functions like sys_mbox_set_invalid() don't need to be
>> thread-safe. But, they did add mutexes to make sure that some
>
Am 10.11.2021 um 22:04 schrieb Grant Edwards:
On 2021-11-10, goldsi...@gmx.de wrote:
Am 10.11.2021 um 20:43 schrieb Grant Edwards:
I'm workikng on a port done by somebody else, and they seem to have
assumed that functions like sys_mbox_set_invalid() don't need to be
thread-safe. But, they
On 2021-11-10, goldsi...@gmx.de wrote:
>
>> I mean can two invocations of the sys_* (mailbox, mutex or semaphore)
>> functions happen "at the same time". For example: can the execution
>> of one call to sys_{sem,mutex,mbox}_set_invalid() be interrupted or
>> suspended by another call to that same
Another porting question, I'm afraid.
In deciding how to implement new/free operations for mailboxes,
semaphores, and mutexes, it would be helpful if I had some idea of
when and how often they are called.
Are execution times for these functions going to noticeably affect
performance of things lik
Hi everyone,
I have a project that is running LwIP V2.1.2. The stack is LwIP on top of
BG96 cellular modem.
It works fine for IPV4, but when I enable IPV6, I only get IPV6 link local
address, and cannot get real IPV6 address, therefore, I cannot connect to
my server.
The LwIP comes from ST cellular
Am 10.11.2021 um 22:34 schrieb Grant Edwards:
[..]
I don't quite understand: what does "points are safe" mean?
I mean for one object, lock/unlock, post/fetch or signal/wait can be
called by multiple threads simultaneously, but deallocation is ensured
to be called from one thread only, when the
Am 10.11.2021 um 22:45 schrieb Grant Edwards:
Another porting question, I'm afraid.
In deciding how to implement new/free operations for mailboxes,
semaphores, and mutexes, it would be helpful if I had some idea of
when and how often they are called.
Are execution times for these functions goin
12 matches
Mail list logo
