On 2022-02-19, Massimiliano Cialdi wrote:
> Okay. Could you give me a suggestion on how I can implement an
> equivalent `select` with in netconn. Keep in mind that I use
> FreeRTOS.
You can use netconn callbacks to wake the relevent thread when a
socket has data to be read. I used a semaphore,
On Sat, Feb 19, 2022 at 10:02 PM goldsi...@gmx.de wrote:
> Well, there's still an undone task in our tracker to convert the socket
> API to just be a "copying" wrapper around the netconn API.
> Unfortunately, it's not like that now and select is not available for
> netconns, yet.
Okay. Could you
Am 19.02.2022 um 21:50 schrieb Massimiliano Cialdi:
On Sat, Feb 19, 2022 at 9:38 PM goldsi...@gmx.de wrote:
The easiest way probably might be to implement a socket read function
that returns netbufs instead of the standard socket read function. But
that's not implemented yet.
Alternatively I
On Sat, Feb 19, 2022 at 9:38 PM goldsi...@gmx.de wrote:
> The easiest way probably might be to implement a socket read function
> that returns netbufs instead of the standard socket read function. But
> that's not implemented yet.
Alternatively I could replace the socket API of the project I'm
Am 19.02.2022 um 20:12 schrieb Massimiliano Cialdi:
I'm trying to port a project to lwip. This project uses BSD sockets
calls, so first, I used lwip's socket APIs.
The project I'm trying to port has to deal with packet timestamping,
that's why I used LWIP_PBUF_CUSTOM_DATA as explained here
I'm trying to port a project to lwip. This project uses BSD sockets
calls, so first, I used lwip's socket APIs.
The project I'm trying to port has to deal with packet timestamping,
that's why I used LWIP_PBUF_CUSTOM_DATA as explained here
https://savannah.nongnu.org/bugs/?55078
This way I can
