From: "Thomas Bächler" <thomas@archlinux.org>
To: Matt Fleming <matt.fleming@intel.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Thomas Bächler" <thomas@archlinux.org>
Subject: [PATCH] efi: Clarify Kconfig help for EFI_MIXED
Date: Fri, 11 Apr 2014 19:59:14 +0200 [thread overview]
Message-ID: <1397239154-30121-1-git-send-email-thomas@archlinux.org> (raw)
EFI stub support is only missing for a 64 bit kernel on 32-bit firmware,
on 64-bit kernels, EFI stub works as usual.
---
Matt, I don't know if this help was intentionally discouraging,
however, out of curiosity, I tested this with ovmf, and the
kernel boots fine on 64-bit firmware bit with EFI stub, and on
32-bit firmware using efilinux.
Documenting this properly is important for distribution kernels.
We would want to support this on Arch, but not if it means
introducing a regression for EFI stub users.
arch/x86/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 5b8ec0f..2bbbbb9 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1529,8 +1529,8 @@ config EFI_MIXED
mode.
Note that it is not possible to boot a mixed-mode enabled
- kernel via the EFI boot stub - a bootloader that supports
- the EFI handover protocol must be used.
+ kernel via the EFI boot stub on 32-bit firmware - a bootloader
+ that supports the EFI handover protocol must be used.
If unsure, say N.
--
1.9.2
next reply other threads:[~2014-04-11 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 17:59 Thomas Bächler [this message]
2014-04-11 18:03 ` [PATCH] efi: Clarify Kconfig help for EFI_MIXED H. Peter Anvin
2014-04-11 18:44 ` Matt Fleming
2014-04-14 7:15 ` Ingo Molnar
2014-04-14 8:28 ` Thomas Bächler
2014-04-14 9:33 ` Matt Fleming
2014-04-14 9:47 ` Borislav Petkov
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=1397239154-30121-1-git-send-email-thomas@archlinux.org \
--to=thomas@archlinux.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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