On 2006-11-17, David Brownell wrote:
> Index: g26/Documentation/rtc.txt
Just another emacs visiting...
Will try to build and reboot to test stuff tomorrow.
Index: 2.6_current/Documentation/rtc.txt
===================================================================
--- 2.6_current.orig/Documentation/rtc.txt 2006-11-17 13:33:10.979411250
+0100
+++ 2.6_current/Documentation/rtc.txt 2006-11-17 13:33:40.981286250 +0100
@@ -18,7 +18,7 @@
* /dev/rtc ... is the RTC provided by PC compatible systems,
so it's not very portable to non-x86 systems.
-
+
* /dev/rtc0, /dev/rtc1 ... are part of a framework that's
supported by a wide variety of RTC chips on all systems.
@@ -86,9 +86,9 @@
interrupt handler is only a few lines of code to minimize any possibility
of this effect.
-Also, if the kernel time is synchronized with an external source, the
-kernel will write the time back to the CMOS clock every 11 minutes. In
-the process of doing this, the kernel briefly turns off RTC periodic
+Also, if the kernel time is synchronized with an external source, the
+kernel will write the time back to the CMOS clock every 11 minutes. In
+the process of doing this, the kernel briefly turns off RTC periodic
interrupts, so be aware of this if you are doing serious work. If you
don't synchronize the kernel time with an external source (via ntp or
whatever) then the kernel will keep its hands off the RTC, allowing you
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
