Update README

[linuxjm/LDP_man-pages.git] / original / man4 / rtc.4

diff --git a/original/man4/rtc.4 b/original/man4/rtc.4
index e67eec6..5a94835 100644 (file)
--- a/original/man4/rtc.4
+++ b/original/man4/rtc.4
@@ -1,6 +1,7 @@
 .\" rtc.4
 .\" Copyright 2002 Urs Thuermann (urs@isnogud.escape.de)
 .\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
 .\" This is free documentation; you can redistribute it and/or
 .\" modify it under the terms of the GNU General Public License as
 .\" published by the Free Software Foundation; either version 2 of
@@ -17,9 +18,9 @@
 .\" GNU General Public License for more details.
 .\"
 .\" You should have received a copy of the GNU General Public
-.\" License along with this manual; if not, write to the Free
-.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
-.\" USA.
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
 .\"
 .\" $Id: rtc.4,v 1.4 2005/12/05 17:19:49 urs Exp $
 .\"
@@ -43,7 +44,7 @@ One of these usually has battery backup power so that it tracks the time
 even while the computer is turned off.
 RTCs often provide alarms and other interrupts.
 
-All i386 PCs, and ACPI based systems, have an RTC that is compatible with
+All i386 PCs, and ACPI-based systems, have an RTC that is compatible with
 the Motorola MC146818 chip on the original PC/AT.
 Today such an RTC is usually integrated into the mainboard's chipset
 (south bridge), and uses a replaceable coin-sized backup battery.
@@ -51,13 +52,13 @@ Today such an RTC is usually integrated into the mainboard's chipset
 Non-PC systems, such as embedded systems built around system-on-chip
 processors, use other implementations.
 They usually won't offer the same functionality as the RTC from a PC/AT.
-.SS RTC vs System Clock
+.SS RTC vs system clock
 RTCs should not be confused with the system clock, which is
 a software clock maintained by the kernel and used to implement
 .BR gettimeofday (2)
 and
 .BR time (2),
-as well as setting timestamps on files, etc.
+as well as setting timestamps on files, and so on.
 The system clock reports seconds and microseconds since a start point,
 defined to be the POSIX Epoch: 1970-01-01 00:00:00 +0000 (UTC).
 (One common implementation counts timer interrupts, once
@@ -306,8 +307,8 @@ it will update a designated RTC periodically every 11 minutes.
 To do so, the kernel has to briefly turn off periodic interrupts;
 this might affect programs using that RTC.
 
-An RTC's Epoch has nothing to do with the POSIX Epoch which is only
-used for the system clock.
+An RTC's Epoch has nothing to do with the POSIX Epoch which is
+used only for the system clock.
 
 If the year according to the RTC's Epoch and the year register is
 less than 1970 it is assumed to be 100 years later, that is, between 2000
@@ -317,7 +318,7 @@ Some RTCs support "wildcard" values in alarm fields, to support
 scenarios like periodic alarms at fifteen minutes after every hour,
 or on the first day of each month.
 Such usage is nonportable;
-portable user space code only expects a single alarm interrupt, and
+portable user-space code expects only a single alarm interrupt, and
 will either disable or reinitialize the alarm after receiving it.
 
 Some RTCs support periodic interrupts with periods that are multiples
@@ -327,7 +328,7 @@ programmable output clock signals;
 nonvolatile memory;
 and other hardware
 capabilities that are not currently exposed by this API.
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR date (1),
 .BR adjtimex (2),
 .BR gettimeofday (2),
@@ -336,5 +337,16 @@ capabilities that are not currently exposed by this API.
 .BR time (2),
 .BR gmtime (3),
 .BR time (7),
-.BR hwclock (8),
-/usr/src/linux/Documentation/rtc.txt
+.BR hwclock (8)
+
+.I Documentation/rtc.txt
+in the Linux kernel source tree
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.