I'm intrigued by your use of the word "other" when referring to
interrupts...
If you are properly using lwIP RAW API, then you should NOT be using
interrupts. Maybe your driver, but it won't call any lwIP low-level
function. Will it ? That would be bad...
> NOTE 1: It is not ideal but I don't
Too much code, I won't look at it.
From the wiki:
http://lwip.wikia.com/wiki/Raw/TCP
"The function may return ERR_MEM if no memory was available for closing
the connection. If so, the application should wait and try again either
by using the acknowledgment callback or the polling functionality
Sergio R. Caprile wrote:
> I use an extra CLOSING state, so the poll callback can kick in.
> When closing, if close succeeds, state is CLOSED and everybody is happy.
> Otherwise, state is CLOSING and the poll callback will retry.
While discussing bug #47485, we kind of decided that it would be goo
