From: joeyli <jlee@suse.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "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>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 1/3] rtc-efi: register rtc-efi device when EFI enabled
Date: Sat, 29 Dec 2012 09:00:03 +0800 [thread overview]
Message-ID: <1356742803.6113.245.camel@linux-s257.site> (raw)
In-Reply-To: <E99CBA9F97C3D149AA6B19ED2E277C9B019215CC@BY2PRD0510MB365.namprd05.prod.outlook.com>
於 五，2012-12-28 於 17:43 +0000，Matthew Garrett 提到：
> On Sat, 2012-12-29 at 00:26 +0800, Lee, Chun-Yi wrote:
> > UEFI time services, GetTime(), SetTime(), GetWakeupTime(), SetWakeupTime() are also
> > supported by other non-IA64 architecutre with UEFI BIOS, e.g. x86.
> >
> > This patch changed RTC_DRV_EFI configuration to depend on EFI but not just IA64. It
> > checks efi_enabled flag and efi-rtc driver should enabled.
>
> In theory, certainly - but do we still have machines that explode if the
> get_time call is made? We may also want to think about disabling the
> legacy access to the RTC if the EFI calls are present.
The legacy get_time access on my test machine is work fine, not thing
explode. :-)
Just we have a function want to expose the timezone information to
userspace and also store it.
Thanks a lot!
Joey Lee
next prev parent reply other threads:[~2012-12-29 1:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 16:26 [PATCH 1/3] rtc-efi: register rtc-efi device when EFI enabled 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
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 [this message]
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=1356742803.6113.245.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--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;
as well as URLs for NNTP newsgroup(s).