[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E99CBA9F97C3D149AA6B19ED2E277C9B019215CC@BY2PRD0510MB365.namprd05.prod.outlook.com>
Date: Fri, 28 Dec 2012 17:43:50 +0000
From: Matthew Garrett <matthew.garrett@...ula.com>
To: "Lee, Chun-Yi" <joeyli.kernel@...il.com>
CC: "matt.fleming@...el.com" <matt.fleming@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"Lee, Chun-Yi" <jlee@...e.com>, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Jan Beulich <JBeulich@...e.com>
Subject: Re: [PATCH 1/3] rtc-efi: register rtc-efi device when EFI enabled
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.
Powered by blists - more mailing lists