AVR-Chat

>
>In your example, below, things that don't generate interrupts need to be
>polled.  There is no way to get around that.  In AvrX the way to handle that
>is  to put a little code into the timer interrupt handler that generates the
>"handshake" event when state changes and then have the task wait on the
>handshake event.

Ok, so the timer isr would then be doing the polling, effectively, right?

As I understand it, you would do the status bit checking during the timer int, and say "task 6 and task 8 are ready to run", and I would assume, put their addresses on the stack in reverse order? (or something like that)