From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Fri, 21 Nov 2025 10:31:12 +0000 (+0100)
Subject: man/systemd-boot: say that /EFI/systemd/drivers is for hardware
X-Git-Tag: v259~1^2~3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3e2b026da3ab24366f2693e5b2c6445db07495ac;p=thirdparty%2Fsystemd.git

man/systemd-boot: say that /EFI/systemd/drivers is for hardware

In aad0d11e7c6f1f7dcc7b00173140c74b8abf88cc we stopped supporting XBOOTLDR
with a different fs driver. This was the primary example that comes to mind
when we talk about loading filesystem drivers in the firmware. Since we don't
want people to do load such drivers, use a different example.
---

diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml
index c465d4f4f35..8e385033027 100644
--- a/man/systemd-boot.xml
+++ b/man/systemd-boot.xml
@@ -386,8 +386,8 @@
     <para>During initialization, <command>systemd-boot</command> automatically loads all driver files placed
     in the <filename>/EFI/systemd/drivers/</filename> directory of the ESP. The files placed there must have
     an extension of the EFI architecture ID followed by <filename>.efi</filename> (e.g. for x86-64 this means
-    a suffix of <filename>x64.efi</filename>). This may be used to automatically load file system drivers and
-    similar, to extend the native firmware support.</para>
+    a suffix of <filename>x64.efi</filename>). This may be used e.g. to add support for hardware not
+    supported natively by the firmware.</para>
 
     <para>Enrollment of Secure Boot variables can be performed manually or automatically if files are available
     under <filename>/loader/keys/<replaceable>NAME</replaceable>/{db,dbx,KEK,PK}.auth</filename>, <replaceable>NAME</replaceable>