People,
I am implementing a "bare metal" (well not really, but that's not the
point) system which is :
- non-preempting multithreaded (no other thread runs before a yield() or
some waiting function)
- Single processor
- All "threads" run with interrupts disabled
- Interrupts have their own c
Hi Ivan,
On Tue, Nov 06, 2018 at 09:52:24AM +0100, Ivan Warren wrote:
>
> My questions are :
>
> - How often should I invoke sys_check_timeouts() (every ms, every 10 ms,
> every second) - or (better) is there a way to determine (after any state
> change obviously) when the next timeout is due ?
Le 11/6/2018 à 10:08 AM, Sylvain Rochet a écrit :
Hi Ivan,
Is sys_timeouts_sleeptime what you are looking for ?
Exactly what I was looking for !
No problem, there are not strict timers in a IP stack, after all -2.4%
is even better that some internal RC clocks. That's apply to sys_now,
conc
Thanks Dave I will try your suggestion.
On Mon, Nov 5, 2018 at 8:09 PM David M. Zar wrote:
> I had the need for the same functionality.
>
> In etharp.c, at the end of etharp_input, put something like this:
>
> arp_callback(&sipaddr, (const struct eth_addr*)&hdr->shwaddr,
> netif->num, hdr->opc
