Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759427AbXE0Xj3 (ORCPT ); Sun, 27 May 2007 19:39:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753326AbXE0XjV (ORCPT ); Sun, 27 May 2007 19:39:21 -0400 Received: from cavan.codon.org.uk ([217.147.92.49]:52739 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752905AbXE0XjU (ORCPT ); Sun, 27 May 2007 19:39:20 -0400 Date: Mon, 28 May 2007 00:39:11 +0100 From: Matthew Garrett To: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Cc: david-b@pacbell.net Message-ID: <20070527233911.GA23491@srcf.ucam.org> References: <20070527190351.GA21387@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070527190351.GA21387@srcf.ucam.org> User-Agent: Mutt/1.5.12-2006-07-14 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@codon.org.uk Subject: Re: RTC_DRV_CMOS can break userspace interface X-SA-Exim-Version: 4.2.1 (built Tue, 20 Jun 2006 01:35:45 +0000) X-SA-Exim-Scanned: Yes (on vavatch.codon.org.uk) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 966 Lines: 25 On Sun, May 27, 2007 at 08:03:51PM +0100, Matthew Garrett wrote: > (It doesn't really help that rtc-cmos doesn't load on this machine, but > I'll try to track that down later - right now I suspect some sort of PNP > issue) Ah, no, it's because the ioports for the rtc-cmos driver are already claimed by the old driver from CONFIG_RTC. The following configuration is valid in Kconfig: CONFIG_RTC=y CONFIG_RTC_CMOS=m 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... -- Matthew Garrett | mjg59@srcf.ucam.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/