linux-kernel - Re: [PATCH, resend] x86: enable rtc-efi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <4FB271860200007800083D21@nat28.tlf.novell.com>
Date:	Tue, 15 May 2012 14:08:54 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Matthew Garrett" <mjg59@...f.ucam.org>
Cc:	<dannf@...nf.org>, <mingo@...e.hu>, <tglx@...utronix.de>,
	<matt.fleming@...ux.intel.com>, <linux-kernel@...r.kernel.org>,
	<hpa@...or.com>
Subject: Re: [PATCH, resend] x86: enable rtc-efi

>>> On 15.05.12 at 14:38, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Tue, May 15, 2012 at 01:08:22PM +0100, Jan Beulich wrote:
>> Besides a Kconfig change this just requires creating a corresponding
>> platform device.
> 
> I don't think this is a good idea yet - we completely fail to perform 
> timezone handling with the EFI clock, which violates platform 
> expectations. We should fix that up first.

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).

Jan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/