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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 28 Dec 2012 23:39:41 +0000 From: Matthew Garrett <matthew.garrett@...ula.com> To: "H. Peter Anvin" <hpa@...or.com> CC: "Lee, Chun-Yi" <joeyli.kernel@...il.com>, "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>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Jan Beulich <JBeulich@...e.com>, Len Brown <lenb@...nel.org>, Arjan van de Ven <arjan@...radead.org> Subject: Re: [PATCH 1/3] rtc-efi: register rtc-efi device when EFI enabled On Fri, 2012-12-28 at 15:32 -0800, H. Peter Anvin wrote: > No, that is explicitly the ordering that is excludable. Windows uses the UEFI time functions. The fact that they fail for us on a bunch of systems is just another symptom of our general failure to accurately mimic Windows when making runtime calls, and we should just make sure that that gets fixed rather than layering more workarounds on top. It's an embarrassment that we're still unable to deal with platforms that work fine with another OS.
Powered by blists - more mailing lists