From: Alan Ott <alan@softiron.co.uk>
To: Matt Fleming <matt@codeblueprint.co.uk>,
Jonathan Corbet <corbet@lwn.net>
Cc: Roy Franz <roy.franz@linaro.org>,
linux-efi@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Alan Ott <alan@softiron.co.uk>
Subject: [PATCH] doc: efi-stub.txt: Fix arm64 paths
Date: Sat, 28 Nov 2015 11:03:23 -0500 [thread overview]
Message-ID: <1448726603-17600-1-git-send-email-alan@softiron.co.uk> (raw)
Update documented paths for arm64 files to match current tree.
---
Documentation/efi-stub.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/efi-stub.txt b/Documentation/efi-stub.txt
index 7747024..e157469 100644
--- a/Documentation/efi-stub.txt
+++ b/Documentation/efi-stub.txt
@@ -10,12 +10,12 @@ arch/x86/boot/header.S and arch/x86/boot/compressed/eboot.c,
respectively. For ARM the EFI stub is implemented in
arch/arm/boot/compressed/efi-header.S and
arch/arm/boot/compressed/efi-stub.c. EFI stub code that is shared
-between architectures is in drivers/firmware/efi/efi-stub-helper.c.
+between architectures is in drivers/firmware/efi/libstub.
For arm64, there is no compressed kernel support, so the Image itself
masquerades as a PE/COFF image and the EFI stub is linked into the
kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
-and arch/arm64/kernel/efi-stub.c.
+and drivers/firmware/efi/libstub/arm64-stub.c.
By using the EFI boot stub it's possible to boot a Linux kernel
without the use of a conventional EFI boot loader, such as grub or
--
2.5.0
next reply other threads:[~2015-11-28 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 16:03 Alan Ott [this message]
2015-11-28 16:12 ` Alan Ott
2015-11-30 11:28 ` Matt Fleming
2015-11-30 11:32 ` Matt Fleming
2015-11-30 14:36 ` [PATCH v2] " Alan Ott
2015-12-02 9:24 ` 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=1448726603-17600-1-git-send-email-alan@softiron.co.uk \
--to=alan@softiron.co.uk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=roy.franz@linaro.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
all inboxes | Powered by JetHome®