From: "Pali Rohár" <pali.rohar@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Austin S Hemmelgarn <ahferroin7@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
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: Tue, 11 Nov 2014 12:53:09 +0100 [thread overview]
Message-ID: <201411111253.10519@pali> (raw)
In-Reply-To: <20141111113831.1119720e@alan.etchedpixels.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 612 bytes --]
On Tuesday 11 November 2014 12:38:31 One Thousand Gnomes wrote:
> > > 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.
>
> I don't believe there is anything which prevents the CSM from
> faking a CMOS clock using SMM from whatever is actually in
> the hardware.
>
> Alan
Also in case when we do not know what SMM code is doing...
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-11-11 11:53 UTC|newest]
Thread overview: 27+ 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 12:32 ` Matt Fleming
[not found] ` <1412339576-17972-1-git-send-email-matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-10-03 15:01 ` Mark Salter
2014-10-03 15:01 ` Mark Salter
[not found] ` <1412348517.5410.13.camel-PDpCo7skNiwAicBL8TP8PQ@public.gmane.org>
2014-11-09 17:37 ` Pali Rohár
2014-11-09 17:37 ` Pali Rohár
2014-11-09 18:22 ` Borislav Petkov
2014-11-09 18:22 ` Borislav Petkov
[not found] ` <20141109182231.GA29337-fF5Pk5pvG8Y@public.gmane.org>
2014-11-10 11:22 ` Matt Fleming
2014-11-10 11:22 ` Matt Fleming
[not found] ` <1415618533.14686.239.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-10 16:23 ` Pali Rohár
2014-11-10 16:23 ` Pali Rohár
2014-11-10 16:45 ` Austin S Hemmelgarn
[not found] ` <5460EB92.1090501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-10 17:04 ` Matthew Garrett
2014-11-10 17:04 ` Matthew Garrett
2014-11-10 20:37 ` Austin S Hemmelgarn
[not found] ` <5461220E.20605-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-10 20:58 ` H. Peter Anvin
2014-11-10 20:58 ` H. Peter Anvin
[not found] ` <546126FF.3070600-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2014-11-10 21:26 ` Matthew Garrett
2014-11-10 21:26 ` Matthew Garrett
2014-11-11 11:38 ` One Thousand Gnomes
2014-11-11 11:38 ` One Thousand Gnomes
2014-11-11 11:46 ` Borislav Petkov
2014-11-11 11:53 ` Pali Rohár [this message]
2014-11-11 12:14 ` Austin S Hemmelgarn
2014-11-14 11:21 ` Pali Rohár
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=201411111253.10519@pali \
--to=pali.rohar@gmail.com \
--cc=a.zummo@towertech.it \
--cc=ahferroin7@gmail.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.