On Friday 28 March 2008, Ingo Molnar wrote:...could you please provide an URL or the patch itself so that others who hit this issue and read this thread can apply the fix?Could somebody please fix the RTC mess in kconfig now ?My version has been sitting in MM for a while now.
I merged the two patches (gentle, then harsh) so the result is
smaller. Here you go.
- dave
========== CUT HERE
Prevent the most significant RTC configuration problems:
- If the new RTC framework is enabled, don't allow any of the
legacy drivers to be configured.
- When using generic RTC on x86, enable rtc-cmos by default.
It seems too many people are used to enabling a legacy RTC despite the Kconfig help/comments; the gentle approach hasn't worked.
Signed-off-by: David Brownell <dbrownell@xxxxxxxxxxxxxxxxxxxxx>
---
drivers/char/Kconfig | 8 ++++++++
drivers/rtc/Kconfig | 5 +----
2 files changed, 9 insertions(+), 4 deletions(-)
--- linux-2.6.orig/drivers/char/Kconfig 2008-03-28 02:35:58.000000000 -0700
+++ linux-2.6/drivers/char/Kconfig 2008-03-28 02:39:17.000000000 -0700
@@ -704,6 +704,12 @@ config NVRAM
To compile this driver as a module, choose M here: the
module will be called nvram.
+#
+# These legacy RTC drivers just cause too many conflicts with the generic
+# RTC framework ... let's not even try to coexist any more.