Re: [lwip-users] idle connection timeout
Is such thing possible to do in Socket API? Help please. -- View this message in context: http://lwip.100.n7.nabble.com/idle-connection-timeout-tp23252p23325.html Sent from the lwip-users mailing list archive at Nabble.com. ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] poll-function not called
Hi lad tcp_tmr() must be called every TCP_TMR_INTERVAL milliseconds.this is necessary for poll callback. -- View this message in context: http://lwip.100.n7.nabble.com/poll-function-not-called-tp23324p23326.html Sent from the lwip-users mailing list archive at Nabble.com. ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] poll-function not called
OK, thanks, this leaded me into the correct direction: Texas Instrumetns has implemented full poll-functionality but they have set both NO_SYS and NO_SYS_NO_TIMERS to 1 which disables the timers completely. One of both seems to be wrong/superfluid for me... 2014-09-22 9:31 GMT+02:00 mobin.seven mobin.se...@live.com: Hi lad tcp_tmr() must be called every TCP_TMR_INTERVAL milliseconds.this is necessary for poll callback. -- View this message in context: http://lwip.100.n7.nabble.com/poll-function-not-called-tp23324p23326.html Sent from the lwip-users mailing list archive at Nabble.com. ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] Context of poll and recv?
Sergio,
reception is not the problem but transmission. Here I learned I can't
enqueue data fgrom main loop directly. Meanwhile I'm setting a similar flag
and collect all my data from within transmission IRQ context - which works
fine.
Karl
2014-09-17 15:03 GMT+02:00 Sergio R. Caprile scapr...@gmail.com:
Hi Karl,
I'm not trying to teach you how to do things, but I need to ask you if
there is any reason why you can't rise a flag in your eth rx interrupt
and run all lwIP code from the main loop ? (zero latency ?)
Mine (sort of):
void eth_input(ifc)
{
do {
if(!flag)
break;
p = pbuf_alloc();
get frame;
netif-input(p, ifc);
} while(more frames);
}
main()
{
while(1){
eth_input(myeth);
}
}
void rxint()
{
ack;
set flag;
}
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] poll-function not called
Karl Karpfen wrote OK, thanks, this leaded me into the correct direction: Texas Instrumetns has implemented full poll-functionality but they have set both NO_SYS and NO_SYS_NO_TIMERS to 1 which disables the timers completely. One of both seems to be wrong/superfluid for me... I think you should ask it on TI forums. this problem is platform dependent.;) -- View this message in context: http://lwip.100.n7.nabble.com/poll-function-not-called-tp23324p23329.html Sent from the lwip-users mailing list archive at Nabble.com. ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] poll-function not called
You could try the way we vendor-agnostic use the stack: Once you set NO_SYS_NO_TIMERS = 0, add a call to sys_check_timeouts() in your main loop. This is the 1.4 way of checking all the timers, including DHCP. This should take care of TCP and so calling your poll function callback for your application. If that doesn't help, then you should ask in the TI forum as mobin.seven said. Anyway, keep us posted so the next victim can find it in the list, and/or the FAQ keeps growing. ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] poll-function not called
Sergio R. Caprile wrote: You could try the way we vendor-agnostic use the stack: Once you set NO_SYS_NO_TIMERS = 0, add a call to sys_check_timeouts() in your main loop. This is the 1.4 way of checking all the timers, including DHCP. This should take care of TCP and so calling your poll function callback for your application. Wasn't that Karl where everything runs in interrupt context? If so, calling sys_check_timeouts() from the main loop while everything else in lwIP runs in interrupt context will surely lead to problems. Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] poll-function not called
Yes Simon, it was Karl. Maybe that is the reason why TI disabled the timers... I would have expected that from a teenager, not from TI... anyway, Karl said he was buffering at interrupts and calling lwIP at main loop (or so I understood). So... Karl: you must call sys_check_timeouts() from the same scope you are calling all other lwIP routines... or ask TI where to, if possible... or use a vendor-agnostic port, like mine: http://scaprile.ldir.com.ar/cms/category/os/lwip-port/ ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
