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
Date: Tue, 15 May 2012 14:22:53 +0100 [thread overview]
Message-ID: <4FB274CD0200007800083D41@nat28.tlf.novell.com> (raw)
In-Reply-To: <20120515131637.GA26038@srcf.ucam.org>
>>> 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
next prev parent reply other threads:[~2012-05-15 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 12:08 Jan Beulich
2012-05-15 12:38 ` Matthew Garrett
2012-05-15 12:41 ` Matt Fleming
2012-05-15 12:50 ` Matthew Garrett
2012-05-15 13:08 ` Jan Beulich
2012-05-15 13:16 ` Matthew Garrett
2012-05-15 13:22 ` Jan Beulich [this message]
2012-05-15 13:26 ` Matthew Garrett
2012-05-15 13:36 ` Jan Beulich
2012-05-15 13:40 ` Matthew Garrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB274CD0200007800083D41@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=dannf@dannf.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@linux.intel.com \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®