Because CONFIG_RTC_DRV_CMOS was not configured, though
you had several other RTC drivers ready.
Then later you had that enabled, but you also had the
legacy driver enabled:
So that was the driver which succesfully bound to the RTC
(since it's probed first) and prevented the more generic
code from kicking in.
Nobody has yet submitted a patch to help arbitrate between the
legacy and "newfangled" RTC drivers. The general "how to Kconfig"
policy has been to expect a lot (too much?) from users, but this
type of annoyance is too common.
Maybe we need something to more actively avoid the "two drivers"
on PC hardware ... like the appended. (The "comment" is there as
a reminder to folk who still look to that menu for RTC stuff.)
- Dave
--- g26.orig/drivers/char/Kconfig
+++ g26/drivers/char/Kconfig
@@ -715,9 +715,12 @@ config NVRAM
To compile this driver as a module, choose M here: the
module will be called nvram.
+comment "You are using the RTC framework, not the legacy CMOS RTC driver"
+ depends on RTC_DRV_CMOS
+
config RTC
tristate "Enhanced Real Time Clock Support"
- depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV && !ARM && !SUPERH && !S390
+ depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV && !ARM && !SUPERH && !S390 && !RTC_DRV_CMOS
---help---
If you say Y here and create a character special file /dev/rtc with
major number 10 and minor number 135 using mknod ("man mknod"), you
--- g26.orig/drivers/rtc/Kconfig
+++ g26/drivers/rtc/Kconfig
@@ -281,6 +281,7 @@ comment "Platform RTC drivers"
config RTC_DRV_CMOS
tristate "PC-style 'CMOS'"
depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
+ default y if X86
help
Say "yes" here to get direct support for the real time clock
found in every PC or ACPI-based system, and some other boards.
--
