Re: Strange issue after early AP startup

On Wednesday, January 18, 2017 09:00:52 AM Hans Petter Selasky wrote:
> On 01/18/17 02:18, John Baldwin wrote:
> > You might still want to adjust 'nextevent' to schedule the next interrupt
> > to be sooner than 'timerperiod' though.  You could just set 'nextevent' to
> > 'now' in that case instead of 'next'.
> 
> Right, I'll give that a spin. Would have to be "now + 1" instead of 
> "now", due to check before et_start() ?

Ugh, ok.  + 1 with sbintime_t is kind of odd which is why I would have liked
to avoid it, but it seems it is required.

-- 
John Baldwin