lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] upgrade from 1.4.1 to 2.0.3


From: Mattia Settin
Subject: Re: [lwip-users] upgrade from 1.4.1 to 2.0.3
Date: Thu, 8 Mar 2018 12:35:28 +0100

In addition I don't really get why
with NO_SYS = 0 (with FreeRTOS) sys_timeouts_mbox_fetch call sys_check_timeouts() which is the handle timeouts for NO_SYS==1 (without OS)
Probably I have an too old port file for FreeRTOS.
Regards
m

On Thu, Mar 8, 2018 at 9:14 AM, Mattia Settin <address@hidden> wrote:
Yes, but sys_now is required even for timeouts for NO_SYS==0 (LWIP_TIMERS = 1). It this correct ?

On Wed, Mar 7, 2018 at 8:02 PM, address@hidden <address@hidden> wrote:
On 07.03.2018 17:40, Mattia Settin wrote:
[..]
The question is:
It is now mandatory define/use sys_now() ?

You can do without, but a number of features new to 2.0.x (or improved there) require it. Right now, the list is:
- timeouts for NO_SYS==1
- LWIP_SO_SNDTIMEO
- LWIP_SO_LINGER
- lwiperf app
- LWIP_TCP_TIMESTAMPS
- PPPoS

This list can grow longer in the future. As such, we can't ifdef out the prototype for these configs and it's always there. You can try without and you'll get a linker error once you enable code which actually uses it.

Simon

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users



--
Mattia Settin
Software and System Engineer





--
Mattia Settin
Software and System Engineer



reply via email to

[Prev in Thread] Current Thread [Next in Thread]