From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Documentation: add extlinux.conf support description
Date: Fri, 24 Apr 2026 11:19:38 +0300 [thread overview]
Message-ID: <CAP1tNvSv6EFTRVNAovG_PTTedM===Rw=qecGsTMJCysSO6hAbA@mail.gmail.com> (raw)
In-Reply-To: <2a9c9062-621c-4d8d-bbb9-5f979a4da81d@pengutronix.de>
Hello Ahmad.
> 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.
I think this can be done later, so as not to bloat the patch series...
next prev parent reply other threads:[~2026-04-24 8:20 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
2026-04-24 8:19 ` Alexander Shiyan [this message]
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='CAP1tNvSv6EFTRVNAovG_PTTedM===Rw=qecGsTMJCysSO6hAbA@mail.gmail.com' \
--to=eagle.alexander923@gmail.com \
--cc=a.fatoum@pengutronix.de \
--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