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>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: blspec
Date: Mon, 13 Apr 2026 21:35:22 +0200	[thread overview]
Message-ID: <de024775-06e7-4fd6-a247-22b702f4aa96@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvS6Hb4rufVCMogNEjYtZ+O=w55fcpeFZVp+PAqtMsOcJg@mail.gmail.com>

Hello,

On 4/13/26 21:15, Alexander Shiyan wrote:
> Hello Ahmad.
> 
> Is it possible to implement a similar provider that parses extlinux.conf
> (i.e. finds DEFAULT, reads the corresponding LABEL section, extracts
> KERNEL, INITRD, APPEND) and creates boot records based on it?

Sure, you can implement a custom `struct bootscanner` and do whatever
you like.

We already have a driver handling the U-Boot environment, so I don't see
why an optional extlinux.conf parser shouldn't be appropriate for upstream
if someone contributes it.

Cheers,
Ahmad

> 
> Thanks!
> 
> пн, 13 апр. 2026 г. в 17:01, Ahmad Fatoum <a.fatoum@pengutronix.de>:
>>
>> Hello Alexander,
>>
>> On 4/10/26 4:02 PM, Alexander Shiyan wrote:
>>> Hello All.
>>>
>>> Can anyone explain how to use the built-in blspec support?
>>> I would like to try setting up booting via exlinux.conf...
>>
>> exlinux.conf and bootloader spec are different formats.
>>
>> Here's a bootloader spec example:
>>
>>   $ cat /loader/entries/imx8mp-evk.conf
>>   title           PTXdist - Pengutronix-DistroKit imx8mp-evk
>>   version         6.18
>>   options         rootwait
>>   linux           /boot/Image
>>   devicetree      /boot/imx8mp-evk.dtb
>>   linux-appendroot        true
>>
>>
>> You can have multiple files under /loader/entries and barebox will
>> iterate over them, extract the compatible of the referenced devicetree,
>> compare it against its own and then decide what to boot.
>>
>> The linux-appendroot key is barebox-specific and means barebox should
>> fixup root= according to the device it found the bootloader spec file
>> on. This is useful for the case where the bootloader spec files are
>> directly in the rootfs and not in a separate partition.
>>
>> Cheers,
>> Ahmad
>>
>>
>>
>>>
>>> Thanks!
>>>
>>>
>>
>> --
>> 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 |
>>
> 


-- 
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-13 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 14:02 blspec Alexander Shiyan
2026-04-13 14:01 ` blspec Ahmad Fatoum
2026-04-13 19:15   ` blspec Alexander Shiyan
2026-04-13 19:35     ` Ahmad Fatoum [this message]

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=de024775-06e7-4fd6-a247-22b702f4aa96@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