i'll check deeply lwip code... you are right! i used your idea! Thanks

Piero

2008/4/24 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:

> Piero 74 wrote:
>
> > LWIP has its task (tcpip thread - i'm using socket), and i saw that this
> > task can block forever trought functions in sys_arch.c sys_arch_sem_wait and
> > sys_arch_mbox_fetch.
> > I implemented these functions putting a macro functions inside a
> > infinite loop (execute if timeout parameter is 0).
> >
> Why don't you simply use sys_timeout to get your triggering function
> called periodically? It puts a callback on a list which is processed by
> sys_sem_wait() before calling sys_arch_sem_wait(). Normally,
> sys_arch_sem_wait() will never be called with infinite timeout from
> tcpip_thread, there are always timeouts running. Look at tcpip.c for
> examples how to use it.
>
>
> Simon
>
>
> _______________________________________________
> lwip-users mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to