Re: [lwip-users] sys_arch_mbox_fetch() implementation for FreeRTOS

sorry, my fault best regards Max Massimiliano Cialdi FIRMWARE ENGINEERING PROFESSIONAL LEADER Powersoft S.p.A. Via E. Conti, 5 - Scandicci (Fi) 50018 - Italy OFFICE:+39 055 7350230 [cid:PS_553e4174-d089-4113-aa68-7863aa6108ea.png]

Re: [lwip-users] sys_arch_mbox_fetch() implementation for FreeRTOS

On 2022-06-21, massimiliano cialdi via lwip-users wrote: > the setsockopt(SO_RCVTIMEO) POSIX call contemplates the possibility > of imposing 0 as the 'timeout' parameter, and in that case that > socket becomes non-blocking (See, for example, > https://stackoverflow.com/questions/49706883/disable

Re: [lwip-users] sys_arch_mbox_fetch() implementation for FreeRTOS

Am 21.06.2022 um 12:37 schrieb massimiliano cialdi via lwip-users: hello, the setsockopt(SO_RCVTIMEO) POSIX call contemplates the possibility of imposing 0 as the 'timeout' parameter, and in that case that socket becomes non-blocking (See, for example, https://stackoverflow.com/questions/4970688

Re: [lwip-users] sys_arch_mbox_fetch() implementation for FreeRTOS

hello, the setsockopt(SO_RCVTIMEO) POSIX call contemplates the possibility of imposing 0 as the 'timeout' parameter, and in that case that socket becomes non-blocking (See, for example, https://stackoverflow.com/questions/49706883/disable-socket-timeout-via-setsockopt). The socket API of lwip