[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49346212.3050102@rtr.ca>
Date: Mon, 01 Dec 2008 17:15:46 -0500
From: Mark Lord <lkml@....ca>
To: Len Brown <lenb@...nel.org>
Cc: Alessandro Zummo <a.zummo@...ertech.it>,
David Brownell <david-b@...bell.net>,
lkml <linux-kernel@...r.kernel.org>, rtc-linux@...glegroups.com,
linux-acpi@...r.kernel.org
Subject: Re: PATCH: /proc/acpi/alarm: handle day-of-month wraparound on readback
Len Brown wrote:
> I don't have a /proc/acpi/alarm due to this:
>
> #if defined(CONFIG_RTC_DRV_CMOS) || defined(CONFIG_RTC_DRV_CMOS_MODULE) ||
> !defined(CONFIG_X86)
> /* use /sys/class/rtc/rtcX/wakealarm instead; it's not ACPI-specific */
> #else
> #define HAVE_ACPI_LEGACY_ALARM
> #endif
..
Yeah.. bit of a nuisance that.
I regularly apply this patch to my own kernels:
--- old/drivers/acpi/sleep/proc.c 2008-01-06 16:39:45.000000000 -0500
+++ linux/drivers/acpi/sleep/proc.c 2008-01-06 17:35:35.000000000 -0500
@@ -78,11 +78,11 @@
}
#endif /* CONFIG_ACPI_PROCFS */
-#if defined(CONFIG_RTC_DRV_CMOS) || defined(CONFIG_RTC_DRV_CMOS_MODULE) || !defined(CONFIG_X86)
+//#if defined(CONFIG_RTC_DRV_CMOS) || defined(CONFIG_RTC_DRV_CMOS_MODULE) || !defined(CONFIG_X86)
/* use /sys/class/rtc/rtcX/wakealarm instead; it's not ACPI-specific */
-#else
+//#else
#define HAVE_ACPI_LEGACY_ALARM
-#endif
+//#endif
#ifdef HAVE_ACPI_LEGACY_ALARM
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists