From: "H. Peter Anvin" <hpa@zytor.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Matt Fleming" <matt.fleming@intel.com>,
"Borislav Petkov" <bp@alien8.de>,
"Mark Salter" <msalter@redhat.com>,
"Alessandro Zummo" <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, "Dave Young" <dyoung@redhat.com>
Subject: Re: [PATCH] rtc: Disable EFI rtc for x86
Date: Mon, 10 Nov 2014 12:58:39 -0800 [thread overview]
Message-ID: <546126FF.3070600@zytor.com> (raw)
In-Reply-To: <5461220E.20605@gmail.com>
On 11/10/2014 12:37 PM, Austin S Hemmelgarn wrote:
> On 2014-11-10 12:04, Matthew Garrett wrote:
>> On Mon, Nov 10, 2014 at 11:45:06AM -0500, Austin S Hemmelgarn wrote:
>>
>>> I agree, without it you need PC CMOS RTC support to access the RTC
>>> on most systems, which in turn means that you have to enable the CSM
>>> in the EFI firmware, which is annoying cause you can't easily dual
>>> boot windows with secure boot when the CSM is enabled.
>>
>> CMOS RTC support doesn't depend on the CSM.
>>
> That's really interesting, because with it compiled in, I can't boot on
> my EFI based thinkpad laptop without telling EFI to launch the CSM, and
> with it compiled out, I can boot fine without the CSM. I'll have to
> look further into the options I have set in my kernel build, I may have
> changed something else without remembering between booting with and
> without the CSM enabled.
>
It could also be that the non-CSM BIOS somehow remaps the CMOS registers.
-hpa
next prev parent reply other threads:[~2014-11-10 20:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 12:32 [PATCH] rtc: Disable EFI rtc for x86 Matt Fleming
2014-10-03 15:01 ` Mark Salter
2014-11-09 17:37 ` Pali Rohár
2014-11-09 18:22 ` Borislav Petkov
2014-11-10 11:22 ` Matt Fleming
2014-11-10 16:23 ` Pali Rohár
2014-11-10 16:45 ` Austin S Hemmelgarn
2014-11-10 17:04 ` Matthew Garrett
2014-11-10 20:37 ` Austin S Hemmelgarn
2014-11-10 20:58 ` H. Peter Anvin [this message]
2014-11-10 21:26 ` Matthew Garrett
2014-11-11 11:38 ` One Thousand Gnomes
2014-11-11 11:46 ` Borislav Petkov
2014-11-11 11:53 ` Pali Rohár
2014-11-11 12:14 ` Austin S Hemmelgarn
2014-11-14 11:21 ` Pali Rohár
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=546126FF.3070600@zytor.com \
--to=hpa@zytor.com \
--cc=a.zummo@towertech.it \
--cc=ahferroin7@gmail.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=msalter@redhat.com \
--cc=pali.rohar@gmail.com \
--cc=rtc-linux@googlegroups.com \
/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).