Re: [lwip-users] Assert after dropped TX packet

2011-10-25 Thread Kieran Mansley
On Thu, 2011-10-20 at 15:14 -0500, Dittrich, Matthew wrote: > Any hints would be greatly appreciated... Sorry for the long post, I > hope you made it through the whole thing! This ended up much longer > than I intended. I think chaining the pbufs as you are in the received callback is fine. Once l

Re: [lwip-users] Assert after dropped TX packet

2011-10-27 Thread Kieran Mansley
On 25 Oct 2011, at 19:42, Dittrich, Matthew wrote: > I can assure you I am not in the stack from different threads. I am using > the raw API in order to avoid creating a task per connection. My Ethernet > task loop consists of a "handle_packets()", see below, netif->input is > ethernet_input(

Re: [lwip-users] Assert after dropped TX packet

2011-10-27 Thread Dittrich, Matthew
uled to be sent again. I don't have faith that the "old" driver would actually send it at that time... Thanks again, MD -Original Message- From: lwip-users-bounces+mdittrich=dukane@nongnu.org [mailto:lwip-users-bounces+mdittrich=dukane....@nongnu.org] On Behalf Of K

Re: [lwip-users] Assert after dropped TX packet

2011-11-01 Thread Kieran Mansley
On Thu, 2011-10-27 at 14:53 -0500, Dittrich, Matthew wrote: > > No other tasks/threads are involved, iqe_monitor_events() and > ethernetif_handlepackets() were discussed/posted previously. The only > place netif->input is called is in ethernetif_handlepackets(), any > application tcp_write()'s th