From: "tip-bot2 for Ahmad Fatoum" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Borislav Petkov <bp@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/misc] Documentation/x86/boot: Peserve type_of_loader=13 for barebox
Date: Mon, 17 Oct 2022 08:47:52 -0000 [thread overview]
Message-ID: <166599647272.401.15990841004146726447.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20221002125752.3400831-1-a.fatoum@pengutronix.de>
The following commit has been merged into the x86/misc branch of tip:
Commit-ID: f0a8dec99a55aee896a1e6739ecf737f4524094a
Gitweb: https://git.kernel.org/tip/f0a8dec99a55aee896a1e6739ecf737f4524094a
Author: Ahmad Fatoum <a.fatoum@pengutronix.de>
AuthorDate: Sun, 02 Oct 2022 14:57:53 +02:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Mon, 17 Oct 2022 10:11:09 +02:00
Documentation/x86/boot: Peserve type_of_loader=13 for barebox
barebox[1], a bootloader for mostly ARM and MIPS embedded systems, can
also be built as EFI payload for x86[2] to provide redundant power-fail
safe, watchdog-supervised boot up.
Since its v2015.09.0 release, it has been booting Linux on x86 with
type_of_loader=0xff[3]. Reserve 13, the next free id, so that can be
used instead in the future.
[1]: https://www.barebox.org/
[2]: https://www.barebox.org/doc/latest/boards/efi.html
[3]: https://elixir.bootlin.com/barebox/v2022.09.0/source/common/efi/payload/image.c#L217
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/20221002125752.3400831-1-a.fatoum@pengutronix.de
---
Documentation/x86/boot.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/x86/boot.rst b/Documentation/x86/boot.rst
index 894a198..240d084 100644
--- a/Documentation/x86/boot.rst
+++ b/Documentation/x86/boot.rst
@@ -455,6 +455,7 @@ Protocol: 2.00+
11 Minimal Linux Bootloader
<http://sebastian-plotz.blogspot.de>
12 OVMF UEFI virtualization stack
+ 13 barebox
== =======================================
Please contact <hpa@zytor.com> if you need a bootloader ID value assigned.
next prev parent reply other threads:[~2022-10-17 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 12:57 [PATCH v2] Documentation: x86: boot: reserve " Ahmad Fatoum
2022-10-17 8:47 ` tip-bot2 for Ahmad Fatoum [this message]
2022-10-17 8:51 ` [tip: x86/misc] Documentation/x86/boot: Peserve " Ahmad Fatoum
2022-10-17 9:23 ` Borislav Petkov
2022-10-17 9:30 ` [tip: x86/misc] Documentation/x86/boot: Reserve " tip-bot2 for Ahmad Fatoum
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=166599647272.401.15990841004146726447.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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
all inboxes | Powered by JetHome®