mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>,
	barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Documentation: add extlinux.conf support description
Date: Wed, 22 Apr 2026 11:14:38 +0200	[thread overview]
Message-ID: <2a9c9062-621c-4d8d-bbb9-5f979a4da81d@pengutronix.de> (raw)
In-Reply-To: <20260416134518.3282395-2-eagle.alexander923@gmail.com>

Hi,

On 4/16/26 3:45 PM, Alexander Shiyan wrote:
> Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>

Thanks for adding documentation.

I have been wanting to add bootloader spec support to openembedded-core
to barebox can be used to boot Beaglebone black images generated by it,
but with extlinux support in barebox that should work as well.
I will surely give this a try in the future.

Could I motivate you to add a self test that exercises the parser?

Doesn't have to be anything extensive, see test/self/blspec.c for an
example. It's basically adding a few configs into the barebox
environment, calling bootentry_create_from_name() on the directory and
then running some assertions.

Thanks,
Ahmad

> ---
>  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

-- 
Pengutronix e.K.                  |                             |
Steuerwalder Str. 21              | http://www.pengutronix.de/  |
31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2026-04-22  9:15 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 ` [PATCH 2/2] Documentation: add extlinux.conf support description Alexander Shiyan
2026-04-22  9:14   ` Ahmad Fatoum [this message]
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=2a9c9062-621c-4d8d-bbb9-5f979a4da81d@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.com \
    /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