From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lowell Gilbert References: <44eflvcaft.fsf@lowell-desk.lan> <31210f5e-1137-54e8-9e22-7562de250614@xenomai.org> <115c0698-ad5f-2dae-4ed4-1e027839eae1@xenomai.org> <44d11e1akp.fsf@be-well.ilk.org> Date: Fri, 09 Feb 2018 10:00:26 -0500 In-Reply-To: <44d11e1akp.fsf@be-well.ilk.org> (Lowell Gilbert's message of "Fri, 09 Feb 2018 09:50:30 -0500") Message-ID: <448tc21a45.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Xenomai] rtdm_timer_start latency? List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lowell Gilbert Cc: xenomai@xenomai.org Lowell Gilbert writes: > To put it another way, I'm trying to figure out what am I doing wrong in: > ret = rtdm_timer_start(&pstate.collect.timer, rtdm_clock_read() + 1, > pstate.collect.period, > RTDM_TIMERMODE_RELATIVE); On second thought, and application of more coffee, that's clearly wrong. My putting a zero in for the second parameter (as I did originally) seems like what I would expect to work.