From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matt Fleming <matt@console-pimps.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Corentin Chary <corentincj@iksaif.net>,
Matthew Garrett <mjg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
Alessandro Crismani <alessandro.crismani@gmail.com>,
Mikhail Bakhterev <mike.bakhterev@gmail.com>,
Patrick H <kernel@feystorm.net>, "H. Peter Anvin" <hpa@zytor.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] samsung-laptop: Disable if CONFIG_EFI=y
Date: Mon, 5 Nov 2012 12:07:36 +0000 [thread overview]
Message-ID: <20121105120736.33af173b@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1352116219.14888.262.camel@mfleming-mobl1.ger.corp.intel.com>
> There is the 'efi_enabled' variable, but it doesn't strictly mean
> "this_is_a_uefi_system()", it actually means "Do we have EFI runtime
> services?". The whole thing is a bit of a mess and I'm planning on
> cleaning it up this week.
As far as I can understand it we should be reserving those areas on a
UEFI booted machine and just marking them as busy so that they are not
available to any drivers to go peering into.
Alan
next prev parent reply other threads:[~2012-11-05 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 17:35 [PATCH] samsung-laptop: Disable if CONFIG_EFI=y Matt Fleming
2012-11-04 17:44 ` Corentin Chary
[not found] ` <CAHR064isMXk8qkqhBJ==9sRRP7xC_j_K5rqXApza-LNkosp5mg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-04 19:37 ` Alan Cox
2012-11-05 9:12 ` Corentin Chary
2012-11-05 10:30 ` Greg KH
2012-11-05 11:50 ` Matt Fleming
2012-11-05 12:07 ` Alan Cox [this message]
2012-11-05 12:09 ` Matt Fleming
2012-11-05 12:12 ` Matt Fleming
2012-11-05 12:13 ` Matt Fleming
2012-11-04 17:47 ` Jonathan Nieder
[not found] ` <20121104174713.GA28414-fcEM2ccDkbL2nhBuCrrZHw@public.gmane.org>
2012-11-04 20:58 ` Matt Fleming
2012-11-05 10:37 ` Greg KH
2012-11-05 12:09 ` Matt Fleming
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=20121105120736.33af173b@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alessandro.crismani@gmail.com \
--cc=corentincj@iksaif.net \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kernel@feystorm.net \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mike.bakhterev@gmail.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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