Message-Id: <4FB274CD0200007800083D41@nat28.tlf.novell.com>
Date: Tue, 15 May 2012 14:22:53 +0100
From: "Jan Beulich" <JBeulich@suse.com>
To: "Matthew Garrett" <mjg59@srcf.ucam.org>
Cc: <dannf@dannf.org>, <mingo@elte.hu>, <tglx@linutronix.de>,
        <matt.fleming@linux.intel.com>, <linux-kernel@vger.kernel.org>,
        <hpa@zytor.com>
Subject: Re: [PATCH, resend] x86: enable rtc-efi
References: <4FB263560200007800083CB0@nat28.tlf.novell.com>
 <20120515123811.GA25248@srcf.ucam.org>
 <4FB271860200007800083D21@nat28.tlf.novell.com>
 <20120515131637.GA26038@srcf.ucam.org>
In-Reply-To: <20120515131637.GA26038@srcf.ucam.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1002
Lines: 23

>>> On 15.05.12 at 15:16, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Tue, May 15, 2012 at 02:08:54PM +0100, Jan Beulich wrote:
> 
>> So how is this driver okay on ia64 then? It's my understanding
>> that either it's entirely broken, or should be used universally.
>> That's the more that accessing the RTC directly isn't really being
>> permitted by the EFI spec (i.e. using this driver really is a
>> requirement, not an option).
> 
> ia64 is basically never dual booted. If there's an RTC in the ACPI 
> tables then it's completely valid to use the legacy RTC.

I don't think so - the two drivers could end up manipulating the
same piece of hardware, without synchronization. rtc-cmos
really should bail when loaded on an EFI-enabled system.

Jan

--
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/