Re: [lwip-devel] core/timers.c with NO_SYS?

[Simon Goldschmidt]

Leon Woestenberg <address@hidden> wrote:
> That's why in an RTOS environment the interrupt handler must not do
> the actual work; it must schedule a thread that takes the appropriate
> lock, not an interrupt disable lock.
> 
> Doing work in an interrupt handler is a common design mistake; the
> interrupt handler should only make sure the interrupt is silenced
> until serviced by a thread.

So far in theory. In real life, you are sometimes limited by your hardware and 
have no other options but to fetch the packet in the interrupt handler to make 
sure you meet the latency requirements.

> I will start a new effort on a proper RTOS layer on top of the raw API.

I'm looking forward to that. Maybe we can still sort this out so that we have a 
clean design while still allowing the "unclean"design in situations where it is 
needed...

Aside from that, cleaning up the sys.h header file and its usage in the core is 
a good task for 1.4.1, I think.

Simon
>