Re: [lwip-users] 'Avoiding sys_thread_new' and 'RTOS Integration'

> > > I still don't understand the statement I quoted from the documentation. > For example how would one allocate on the stack for sys_mbox_new()? > ​You can't. All you can do in such cases is count how many mboxes/semaphores/threads etc. you need and allocate their storage statically. A call to

Re: [lwip-users] Version 1.5 Mystery

Hi Kenny ST seems to have pulled the git head at some point and continue to distribute that. LWIP_VERSION_RC 0 means development version. 1.5 was never released, it was the next planned release for a while but it was renamed to 2.0. Your options for "known to work up and running" are 1.4.1 or 2.0

[lwip-users] Version 1.5 Mystery

The ST Cube software generated a version of LWIP with version 1.5 but I cannot find such a branch or tag in the git repository. I did find this which suggests that 1.5 was the first version to implement IPV6 and it seems to have been the basis for 2.0. My u

Re: [lwip-users] 'Avoiding sys_thread_new' and 'RTOS Integration'

On nie, 2016-10-09 at 18:36 +, Kenny Koller wrote: > It seems that the conservative thing to do is use the heap to get > started and as I become comfortable with the code base I'll consider > what is required for static allocation. I'll also just let LWIP > create it's own tasks using the C API

Re: [lwip-users] 'Avoiding sys_thread_new' and 'RTOS Integration'

Dirk and Freddy: Thank you for your comments. It seems that the conservative thing to do is use the heap to get started and as I become comfortable with the code base I'll consider what is required for static allocation. I'll also just let LWIP create it's own tasks using the C API. I still don't