[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070528003822.GA23759@srcf.ucam.org>
Date: Mon, 28 May 2007 01:38:23 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Cc: david-b@...bell.net
Subject: Re: RTC_DRV_CMOS can break userspace interface
On Mon, May 28, 2007 at 12:39:11AM +0100, Matthew Garrett wrote:
> but will disable /proc/acpi/wakeup. It'll also be impossible to load
> CONFIG_RTC_CMOS because CONFIG_RTC has grabbed the io ports, so it's not
> possible to use the new interface. This situation doesn't appear to be
> documented, which is less than ideal...
Actually, it seems to be worse than that - the PNP entry for my cmos
clock doesn't appear to mention an irq, so the wakealarm entry doesn't
work. I can happily wake it using the /proc/acpi/alarm interface.
David, would you be happy with hardcoding the rtc-cmos IRQ to 8 on PCs
if there's inadequate PNP information available?
--
Matthew Garrett | mjg59@...f.ucam.org
-
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