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]
Date:	Mon, 9 Jun 2014 13:46:35 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Daniel Kiper <daniel.kiper@...cle.com>
Cc:	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, xen-devel@...ts.xenproject.org,
	boris.ostrovsky@...cle.com, david.vrabel@...rix.com, hpa@...or.com,
	jbeulich@...e.com, konrad.wilk@...cle.com, matt.fleming@...el.com,
	mingo@...hat.com, tglx@...utronix.de
Subject: Re: Why efi_set_rtc_mmss() is never used?

On Mon, 9 Jun 2014 13:08:00 +0200
Daniel Kiper <daniel.kiper@...cle.com> wrote:

> Hi,
> 
> As I can see efi_set_rtc_mmss() is never used to set RTC.
> Even on EFI platform mach_set_rtc_mmss() is called and does
> that thing. Why it is done in that way? It is a bug or it was
> done intentionally. Am I missing something?

EFI services generally don't work properly. The less they are used the
better. We can realistically only make an EFI call with the same
parameters windows does under the same kind of circumstances because the
firmware on many motherboards is complete sh*te.

Alan
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ