From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: barebox@lists.infradead.org
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: [PATCH 2/2] Documentation: add extlinux.conf support description
Date: Thu, 16 Apr 2026 16:45:18 +0300 [thread overview]
Message-ID: <20260416134518.3282395-2-eagle.alexander923@gmail.com> (raw)
In-Reply-To: <20260416134518.3282395-1-eagle.alexander923@gmail.com>
Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
---
Documentation/user/booting-linux.rst | 38 ++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index ed1ec3f68a..307f33bb22 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -306,6 +306,44 @@ Additional notes about keys in the bootloader spec entries:
different devices without having to specify a different ``root=`` option each
time.
+.. _extlinux_conf:
+
+extlinux.conf Support
+^^^^^^^^^^^^^^^^^^^^^
+
+In addition to the Boot Loader Specification, barebox also supports the
+extlinux configuration format, commonly used by the Syslinux bootloader and
+many Linux distributions. This format is often found on SD cards, USB drives,
+or disk partitions prepared with tools like ``extlinux --install``.
+
+The configuration file is named ``extlinux.conf`` and can be located at:
+* ``/boot/extlinux/extlinux.conf``
+
+The file uses a simple key-value syntax with sections labeled by ``LABEL``.
+A typical example looks like:
+
+.. code-block:: none
+
+ DEFAULT linux
+ LABEL linux
+ KERNEL /boot/vmlinuz
+ INITRD /boot/initrd.img
+ FDT /boot/board.dtb
+ APPEND console=ttyS0,115200 root=PARTUUID=deadbeef-01
+
+When booting an extlinux entry, barebox automatically strips any ``root=``
+parameter from the ``APPEND`` line and injects the correct ``root=`` based on
+the boot device (similar to the ``linux-appendroot`` feature in blspec). This
+makes the same root filesystem image usable across different storage media.
+
+To use extlinux support, enable ``CONFIG_EXTLINUX`` in your barebox
+configuration. Entries are automatically discovered by the :ref:`command_boot`
+command when scanning a device or mount point. For example:
+
+.. code-block:: sh
+
+ boot mmc1.2
+
.. _booting_linux_net:
Network boot
--
2.52.0
next prev parent reply other threads:[~2026-04-16 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 13:45 [PATCH 1/2] Add support for extlinux.conf Alexander Shiyan
2026-04-16 13:45 ` Alexander Shiyan [this message]
2026-04-22 9:14 ` [PATCH 2/2] Documentation: add extlinux.conf support description Ahmad Fatoum
2026-04-24 8:19 ` Alexander Shiyan
2026-04-22 9:10 ` [PATCH 1/2] Add support for extlinux.conf Ahmad Fatoum
2026-04-24 8:46 ` Alexander Shiyan
2026-04-24 14:53 ` Ahmad Fatoum
2026-04-27 8:58 ` Sascha Hauer
2026-04-27 17:34 ` Alexander Shiyan
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=20260416134518.3282395-2-eagle.alexander923@gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.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