Commit:     55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f
Parent:     ef154ec69c45aa052b1fa71ee5eeaca7e7f920a3
Author:     David Brownell <[EMAIL PROTECTED]>
AuthorDate: Sat Jul 21 04:37:56 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Sat Jul 21 17:49:17 2007 -0700

    rtc kconfig: point out need for static linkage
    Various people have expressed surprise that their modular RTC drivers don't
    seem to work for initializing the system time at boot.  To help avoid such
    unpleasantness, make the Kconfig text point out that the driver probably
    needs to be statically linked.
    Signed-off-by: David Brownell <[EMAIL PROTECTED]>
    Acked-by: Alessandro Zummo <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 drivers/rtc/Kconfig |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 35f3466..505f512 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -38,6 +38,9 @@ config RTC_HCTOSYS_DEVICE
          clock, usually rtc0.  Initialization is done when the system
          starts up, and when it resumes from a low power state.
+         The driver for this RTC device must be loaded before late_initcall
+         functions run, so it must usually be statically linked.
          This clock should be battery-backed, so that it reads the correct
          time when the system boots from a power-off state.  Otherwise, your
          system will need an external clock source (like an NTP server).
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to