Opened on 12/15/21 at 22:27:35
Closed on 01/26/22 at 18:36:34
#4572 closed defect (fixed)
Improve Clarity for New Clock Manager Directives
Reported by: | Joel Sherrill | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | 6.1 |
Component: | doc | Version: | 6 |
Severity: | normal | Keywords: | qualification |
Cc: | Blocked By: | ||
Blocking: |
Description
Looking through the Clock Manager at the new APIs, I noticed that there is nothing about what bintime and sbintime are in the "Time and Date Data Structures" section. Explaining what these time representations are is needed.
struct timeval and timespec are also not described in "Time and Data Data Structures" but this may be OK since they are from C and/or POSIX.
There is no discussion of what coarse is versus the non-coarse and what this means in practice.
There is no background on what the various clock sources are.
There may be other similar typos but rtems_clock_get_monotonic() describes its sole argument as being of the wrong type.
Without some background on the various time formats, sources, and terminology, the distinction between these APIs and their intended uses is impossible to figure out.
Change History (7)
comment:1 Changed on 12/16/21 at 06:41:56 by Sebastian Huber <sebastian.huber@…>
comment:2 Changed on 12/16/21 at 07:16:25 by Sebastian Huber
Keywords: | qualification added |
---|---|
Status: | assigned → accepted |
comment:3 Changed on 12/16/21 at 14:38:16 by Sebastian Huber <sebastian.huber@…>
comment:5 Changed on 01/11/22 at 08:19:52 by Sebastian Huber <sebastian.huber@…>
comment:6 Changed on 01/26/22 at 13:27:01 by Sebastian Huber
Joel, please close this issue or complain.
comment:7 Changed on 01/26/22 at 18:36:34 by Joel Sherrill
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
I think it covers the concepts now.
In 732d8bc/rtems-docs: