All definitions of the Epoch have been refactored to the following:
1970-01-01 00:00:00 +0000 (UTC)
That form is more consistent, logical, precise, and internationally
recognizable than the other variants.
Also, some wording has been altered as well.
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
- Generalize ... it's not just for PC/AT style RTCs, and there
may be more than one RTC per system.
- Not all RTCs expose the same feature set as PC/AT ones; most
of these ioctls will be rejected by some RTCs.
- Be explicit about when {A,P}IE_{ON,OFF} calls are needed.
- Describe the parameter to the get/set epoch request; correct
the description of the get/set frequency parameter.
- Document RTC_WKALM_{RD,SET}, which don't need AIE_{ON,OFF} and
which support longer alarm periods.
- Hey, not all system clock implementations count timer irqs any
more now that the new RT-derived clock support is merging.