On 2022-01-12, Simon Goldschmidt wrote:
> Am 12. Januar 2022 18:45:44 MEZ schrieb Grant Edwards
> :
>>On 2022-01-12, Sylvain Rochet wrote:
>>
>>> Actually, it should do both. Place the packet in the TX queue and return
>>> immediately, BUT if the queue is full it should wait for a free slot.
Am 12. Januar 2022 18:45:44 MEZ schrieb Grant Edwards
:
>On 2022-01-12, Sylvain Rochet wrote:
>
>> Actually, it should do both. Place the packet in the TX queue and return
>> immediately, BUT if the queue is full it should wait for a free slot.
>
>So, when using an OS, I can assume that lwIP
On 2022-01-12, Sylvain Rochet wrote:
> Actually, it should do both. Place the packet in the TX queue and return
> immediately, BUT if the queue is full it should wait for a free slot.
So, when using an OS, I can assume that lwIP will never call
linkoutput() from a non-thread context or from a
Hi,
On Wed, Jan 12, 2022 at 04:39:30PM -, Grant Edwards wrote:
> What is the expected behavior of the netif linkoutput() function?
>
> Specificallyy, is it expected to
>
> 1) Block until the packet has been sent?
>
> or
>
> 2) Place the packet in a TX queue/fifo and return immediately?
What is the expected behavior of the netif linkoutput() function?
Specificallyy, is it expected to
1) Block until the packet has been sent?
or
2) Place the packet in a TX queue/fifo and return immediately?
All of the Ethernet drivers I've worked on for other RTOSes in the
past couple
