Re: 9.1: boot-time delay? [WORKAROUND FOUND]

[Johnny Billquist <bqt%softjar.se@localhost>]

On 2021-05-27 22:14, Robert Elz wrote:
>      Date:        Thu, 27 May 2021 05:05:15 -0000 (UTC)
>      From:        mlelstv%serpens.de@localhost (Michael van Elst)
>      Message-ID:  <s8n9ab$hs1$1%serpens.de@localhost>
>
>    | And both should be replaced by hztous()/ustohz().
>
> While changing ms to us is probably a good idea, when a change happens,
> the "hz" part should be changed too.

Not sure I agree with that.

> hz is (a unit of) a measure of frequency, ms (or us) is (a unit of) a
> measure of time (duration) - converting one to the other makes no sense.

It sure does. Frequency essentially means a counting of the number of 
time something happens over a specific time period. With hertz, the time 
period is one second. So then converting the number of times an event 
happens in a second into how long it is between two events makes total 
sense.

> What these functions/macros do is convert between ms (or us) and ticks
> (another measure of a duration), not hz, so the misleading "hz" part of
> the name should be removed (changed) if a new macro/function is to be invented.
> (The benefit isn't worth it to justify changing the current existing names,
> but we shouldn't persist with nonsense if we're doing something new.)

A tick is not a duration. A tick is a specific event at a specific time. 
It has no duration. You have a duration between two ticks.

And commonly at every tick you get an interrupt, and you do something, 
and then resume your normal work. The tick has passed. Waiting for the 
next one to happen.

  Johnny

--
Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol