From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
"matt.fleming@intel.com" <matt.fleming@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"Lee, Chun-Yi" <jlee@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Jan Beulich <JBeulich@suse.com>,
Len Brown <lenb@kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH 1/3] rtc-efi: register rtc-efi device when EFI enabled
Date: Fri, 28 Dec 2012 12:40:56 -0800 [thread overview]
Message-ID: <50DE03D8.9030902@zytor.com> (raw)
In-Reply-To: <E99CBA9F97C3D149AA6B19ED2E277C9B019215FA@BY2PRD0510MB365.namprd05.prod.outlook.com>
On 12/28/2012 11:17 AM, Matthew Garrett wrote:
> On Fri, 2012-12-28 at 11:07 -0800, H. Peter Anvin wrote:
>> We do have such machines, which is why this change has been reverted twice already. I believe we should stick to the priority scheme I proposed a few weeks ago.
>
> I seem to have missed that discussion, and couldn't find it after a
> brief search. Got a pointer?
>
Looks like it was a non-public distribution ... anyway, what I wrote was:
> I suspect that what we *should* do looks like:
>
> 1. If ACPI exports a Time and Alarm Device (ACPI000E) the use it;
> 2. If ACPI exports an PC/AT device (PNP0B00/1/2) then use it(*);
> 3. If we have an EFI RTC use it;
> 4. Probe for a PC/AT RTC device.
>
> I'm unsure what the ordering of 1 & 2 should be. The ACPI device has
> the advantage that it contains time zone information, which is important
> for Windows interoperability, and at least optionally supports
> millisecond resolution; there is no way to even export "this is where
> you find time zone information" (since we're dealing with an RTC with
> embedded CMOS, there is storage available, it is just a matter of
> telling the OS how to find it) for the PNP0B0x devices.
>
> The TAD is also guaranteed to map 1:1 to the EFI RTC.
>
> -hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-12-28 20:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 16:26 Lee, Chun-Yi
2012-12-28 16:26 ` [PATCH 2/3] rtc-efi: add timezone to rtc_time that will used by rtc-efi Lee, Chun-Yi
2012-12-28 16:26 ` [PATCH 3/3] rtc-efi: set uie_unsupported for indicate rtc-efi doesn't support UIE mode Lee, Chun-Yi
2012-12-28 17:43 ` [PATCH 1/3] rtc-efi: register rtc-efi device when EFI enabled Matthew Garrett
2012-12-28 19:07 ` H. Peter Anvin
2012-12-28 19:17 ` Matthew Garrett
2012-12-28 20:40 ` H. Peter Anvin [this message]
2012-12-28 20:49 ` Matthew Garrett
[not found] ` <35da3df5-ecac-4b57-83a2-828326e5bfc3@email.android.com>
2012-12-28 23:39 ` Matthew Garrett
2012-12-29 0:42 ` H. Peter Anvin
2012-12-29 4:37 ` Matthew Garrett
2012-12-29 5:19 ` H. Peter Anvin
2012-12-29 6:17 ` Matthew Garrett
2012-12-28 23:44 ` H. Peter Anvin
2013-01-02 2:45 ` joeyli
2013-01-02 7:26 ` Matt Fleming
2012-12-29 1:00 ` joeyli
2012-12-29 1:07 ` H. Peter Anvin
2013-01-09 6:23 ` joeyli
2013-01-09 6:27 ` H. Peter Anvin
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=50DE03D8.9030902@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=arjan@infradead.org \
--cc=jlee@suse.com \
--cc=joeyli.kernel@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matthew.garrett@nebula.com \
--cc=mingo@redhat.com \
--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
Powered by JetHome