Robert Morse wrote:
My driver, in the receive interrupt, just messages a HIGH priority
task, to actually
handle passing the data into the lwip stack.
How specifically does it do that? Does it call etharp_ip_input() directly
for example?
Although I can't see any immediate problem in what is in your description,
this sounds a lot like an inter-thread locking problem of some sort.
I assume you are using the sequential (netconn) API. The most obvious thing
to bear in mind is that the thread-safety is limited - you should only use
one connection in one thread at one time. You can't use the same connection
in two different threads at one time.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------ Opinions==mine
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
